Re: Incorrect assumption in heap_prepare_freeze_tuple

From: Andres Freund <andres(at)anarazel(dot)de>
To: Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Incorrect assumption in heap_prepare_freeze_tuple
Date: 2020-10-03 07:36:19
Message-ID: 20201003073619.dn2zamk4btyxefwe@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2020-10-03 12:58:01 +0530, Kuntal Ghosh wrote:
> IIUC, there can be a HOT-updated tuple which is not initially pruned
> by heap_page_prune but later diagnosed HEAPTUPLE_DEAD by
> HeapTupleSatisfiesVacuum (Since OldestXmin can be updated by the time
> we call HeapTupleSatisfiesVacuum and xmax becomes older than
> OldestXmin).

Hm? OldestXmin is constant over the course of vacuum, no?

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2020-10-03 07:55:59 Re: Resetting spilled txn statistics in pg_stat_replication
Previous Message Kuntal Ghosh 2020-10-03 07:28:01 Re: Incorrect assumption in heap_prepare_freeze_tuple