Re: pg_upgrade fails if vacuum_defer_cleanup_age > 0 - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: pg_upgrade fails if vacuum_defer_cleanup_age > 0
Date
Msg-id 98e32324abcce74c70738fc6c0ed47abe3e686b5.camel@cybertec.at
Whole thread Raw
In response to Re: pg_upgrade fails if vacuum_defer_cleanup_age > 0  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_upgrade fails if vacuum_defer_cleanup_age > 0
List pgsql-hackers
On Mon, 2020-06-15 at 20:59 -0400, Bruce Momjian wrote:
> On Sat, Jun 13, 2020 at 08:46:36AM -0400, Bruce Momjian wrote:
> > On Wed, Jun 10, 2020 at 04:07:05PM +0200, Laurenz Albe wrote:
> > > A customer's upgrade failed, and it took me a while to
> > > figure out that the problem was that they had set
> > > "vacuum_defer_cleanup_age=10000" on the new cluster.
> > > 
> > > The consequence was that the "vacuumdb --freeze" that
> > > takes place before copying commit log files failed to
> > > freeze "pg_database".
> > > That caused later updates to the table to fail with
> > > "Could not open file "pg_xact/0000": No such file or directory."
> > > 
> > > I think it would increase the robustness of pg_upgrade to
> > > force "vacuum_defer_cleanup_age" to 0 on the new cluster.
>
> Thank you, applied to all supported PG versions.

Thanks for picking this up and taking care of it.

Yours,
Laurenz Albe




pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Getting ERROR with FOR UPDATE/SHARE for partitioned table.
Next
From: "李杰(慎追)"
Date:
Subject: 回复:回复:回复:how to create index concurrently on partitioned table