Re: visibility map corruption - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: visibility map corruption
Date
Msg-id 20210707014903.GH26994@momjian.us
Whole thread Raw
In response to Re: visibility map corruption  (Bruce Momjian <bruce@momjian.us>)
Responses Re: visibility map corruption  ("Drouvot, Bertrand" <bdrouvot@amazon.com>)
List pgsql-hackers
On Tue, Jul  6, 2021 at 08:36:13PM -0400, Bruce Momjian wrote:
> On Tue, Jul  6, 2021 at 06:49:10PM -0400, Bruce Momjian wrote:
> > My point is that there are a lot internals involved here that are not
> > part of pg_upgrade, though it probably only affects pg_upgrade.  Anyway,
> > Bertrand patch seems to have what I need.
> 
> One question is how do we want to handle cases where -x next_xid is used
> but -u oldestXid is not used?  Compute a value for oldestXid like we did
> previously?  Throw an error?  Leave oldestXid unchanged?  I am thinking
> the last option.

Here is a modified version of Bertrand's patch, with docs, that does the
last option.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  If only the physical world exists, free will is an illusion.


Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Keep notnullattrs in RelOptInfo (Was part of UniqueKey patch series)
Next
From: Gurjeet Singh
Date:
Subject: Slightly improve initdb --sync-only option's help message