Re: Reducing the WAL overhead of freezing in VACUUM by deduplicating per-tuple freeze plans - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Reducing the WAL overhead of freezing in VACUUM by deduplicating per-tuple freeze plans
Date
Msg-id CAH2-Wzk4MaPYRhb-bzVs5FX0uLuWj3NVFYUCv0t6UqKHR8XZFw@mail.gmail.com
Whole thread Raw
In response to Re: Reducing the WAL overhead of freezing in VACUUM by deduplicating per-tuple freeze plans  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Reducing the WAL overhead of freezing in VACUUM by deduplicating per-tuple freeze plans
List pgsql-hackers
On Fri, Nov 11, 2022 at 10:38 AM Peter Geoghegan <pg@bowt.ie> wrote:
> Attached is v4, which removes the old comments you pointed out were
> now out of place (they weren't adding much anyway). Also fixed bitrot
> against HEAD from today's visibility map commit from Jeff Davis.

Pushed something like this earlier today, though without any changes
to VISIBLE records.

I just started a new thread to discuss standardizing the symbol name
for recovery conflict XID cutoffs reported by tools like pg_waldump.
Seemed better to deal with VISIBLE records in the scope of that new
refactoring patch.

Thanks
-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: List of Bitmapset (was Re: ExecRTCheckPerms() and many prunable partitions)
Next
From: Ted Yu
Date:
Subject: closing file in adjust_data_dir