Re: Incorrect assumption in heap_prepare_freeze_tuple

From: Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Incorrect assumption in heap_prepare_freeze_tuple
Date: 2020-10-04 08:37:15
Message-ID: CAGz5QCJWmrpLTbW2PZ0GV7ocEy4RT_fFAxKFgXJdwC+TqLCT4Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Oct 4, 2020 at 12:33 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> To get to this point heap_page_prune() has to have been called for the
> page. That removes all tuple [versions] that are DEAD. But not
> RECENTLY_DEAD. But RECENTLY_DEAD can only happen for tuples that are
> newere than OldestXmin. Thus the only tuples that the HTSV() we're
> talking about can return DEAD for are ones that were RECENTLY_DEAD
> in heap_page_prune().
>
Got it. Thank you for the explanations. :-)

--
Thanks & Regards,
Kuntal Ghosh

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2020-10-04 09:36:05 Re: Asynchronous Append on postgres_fdw nodes.
Previous Message Andy Fan 2020-10-04 07:10:54 Re: [HACKERS] Runtime Partition Pruning