Re: Eliminate redundant tuple visibility check in vacuum - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Eliminate redundant tuple visibility check in vacuum
Date
Msg-id CA+Tgmobdr_2s09sJkZ-BZL3woZpQJrnkjN3-b1E0GpHEiur+6w@mail.gmail.com
Whole thread Raw
In response to Re: Eliminate redundant tuple visibility check in vacuum  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Sat, Sep 30, 2023 at 1:02 PM Andres Freund <andres@anarazel.de> wrote:
> The only thought I have is that it might be worth to amend the comment in
> lazy_scan_prune() to mention that such a tuple won't need to be frozen,
> because it was visible to another session when vacuum started.

I revised the comment a bit, incorporating that language, and committed.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: David Christensen
Date:
Subject: Re: Initdb-time block size specification
Next
From: Robert Haas
Date:
Subject: Re: [PATCH] Clarify the behavior of the system when approaching XID wraparound