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

From Andres Freund
Subject Re: Eliminate redundant tuple visibility check in vacuum
Date
Msg-id 20230930170243.vg7atbiynrcbo44l@alap3.anarazel.de
Whole thread Raw
In response to Re: Eliminate redundant tuple visibility check in vacuum  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Eliminate redundant tuple visibility check in vacuum
List pgsql-hackers
Hi,

On 2023-09-28 11:25:04 -0400, Robert Haas wrote:
> I went ahead and committed 0001. If Andres still wants to push for
> more renaming there, that can be a follow-up patch.

Agreed.

> And we can see if he or anyone else has any comments on this new version of
> 0002. To me we're down into the level of details that probably don't matter
> very much one way or the other, but others may disagree.

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.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [feature]COPY FROM enable FORCE_NULL/FORCE_NOT_NULL on all columns
Next
From: Andres Freund
Date:
Subject: Re: Annoying build warnings from latest Apple toolchain