Re: visibility map corruption

From: "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Floris Van Nee <florisvannee(at)optiver(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: visibility map corruption
Date: 2021-07-06 19:33:35
Message-ID: 5b57aff3-6557-c393-4451-33a20f690aa9@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 7/6/21 8:57 PM, Tom Lane wrote:
> Peter Geoghegan <pg(at)bowt(dot)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.

FWIW there is a commitfest entry for it:
https://commitfest.postgresql.org/33/3105/

Thanks

Bertrand

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2021-07-06 20:10:02 Re: Using COPY FREEZE in pgbench
Previous Message Jim Mlodgenski 2021-07-06 19:26:16 Re: Hook for extensible parsing.