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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Reducing the WAL overhead of freezing in VACUUM by deduplicating per-tuple freeze plans
Date: 2022-11-15 18:26:05
Message-ID: CAH2-Wzk4MaPYRhb-bzVs5FX0uLuWj3NVFYUCv0t6UqKHR8XZFw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 11, 2022 at 10:38 AM Peter Geoghegan <pg(at)bowt(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ted Yu 2022-11-15 18:43:51 closing file in adjust_data_dir
Previous Message Tom Lane 2022-11-15 18:25:16 Re: List of Bitmapset (was Re: ExecRTCheckPerms() and many prunable partitions)