Re: visibility map corruption - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: visibility map corruption
Date
Msg-id 20210724010118.GE8025@momjian.us
Whole thread Raw
In response to Re: visibility map corruption  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: visibility map corruption
List pgsql-hackers
On Fri, Jul 23, 2021 at 05:47:18PM -0700, Peter Geoghegan wrote:
> > I could perhaps see corruption happening if pg_control's oldest xid
> > value was closer to the current xid value than it should be, but I can't
> > see how having it 2-billion away could cause harm, unless perhaps
> > pg_upgrade itself used enough xids to cause the counter to wrap more
> > than 2^31 away from the oldest xid recorded in pg_control.
> >
> > What I am basically asking is how to document this and what it fixes.
> 
> ISTM that this is a little like commits 78db307bb2 and a61daa14. Maybe
> take a look at those?

Agreed.  I just wanted to make sure I wasn't missing an important aspect
of this patch.  Thanks.

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

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




pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: visibility map corruption
Next
From: Robert Haas
Date:
Subject: Re: Followup Timestamp to timestamp with TZ conversion