Re: recovering from "found xmin ... from before relfrozenxid ..."

From: Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
To: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: recovering from "found xmin ... from before relfrozenxid ..."
Date: 2020-07-31 12:32:24
Message-ID: CAE9k0PnF4wUgPVrQEVjSCgVcLamwX8Bu_jovUuFOnt5Z7+x2pw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 29, 2020 at 9:58 AM Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
wrote:

>
> > I think we should let VACUUM do that.
>> Sometimes VACUUM will not get to these pages, because they are marked All
>> Frozen.
>> An possibly some tuples will get stale on this page again
>>
>
> Hmm, okay, will have a look into this. Thanks.
>

I had a look over this and found that one can use the DISABLE_PAGE_SKIPPING
option with VACUUM to disable all its page-skipping behavior.

--
With Regards,
Ashutosh Sharma
EnterpriseDB:http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2020-07-31 12:36:25 Re: Missing CFI in hlCover()?
Previous Message Georgios 2020-07-31 12:25:02 [PATCH] - Provide robust alternatives for replace_string