Re: visibility map corruption - Mailing list pgsql-hackers

From Tom Lane
Subject Re: visibility map corruption
Date
Msg-id 1744615.1625597820@sss.pgh.pa.us
Whole thread Raw
In response to Re: visibility map corruption  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: visibility map corruption  ("Drouvot, Bertrand" <bdrouvot@amazon.com>)
Re: visibility map corruption  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
Peter Geoghegan <pg@bowt.ie> writes:
> ... We should just carry forward the original oldestXid.

Yup.  It's a bit silly that we recognized the need to do that
for oldestMultiXid yet not for oldestXid.

BTW, is it really necessary for copy_xact_xlog_xid to invoke pg_resetwal
so many times?  Why can't we pass all of the update-this options in one
call?

Who's going to do the legwork on this?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: visibility map corruption
Next
From: Daniel Gustafsson
Date:
Subject: Re: proposal - log_full_scan