Re: pg_upgrade and materialized views

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Claudio Freire <klaussfreire(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_upgrade and materialized views
Date: 2018-02-20 22:29:01
Message-ID: 27849.1519165741@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andres Freund <andres(at)anarazel(dot)de> writes:
> I wonder if there's a scenario in which a schema restore uses enough
> xids to get close to anti-wraparound territory?

Interesting question ... you'd need one heck of a lot of objects in
the cluster, but we've certainly heard of people with lots of objects.

We could stave that problem off by running the restore steps in
--single-transaction mode, if it weren't that pg_restore will reject the
combination of --create and --single-transaction. I wonder if we should
allow that, specifying that it means that the single transaction starts
after we reconnect to the new DB.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Claudio Freire 2018-02-20 22:56:36 Re: pg_upgrade and materialized views
Previous Message Tom Lane 2018-02-20 22:24:03 Re: pg_upgrade and materialized views