Re: PG17 optimizations to vacuum - Mailing list pgsql-general

From Melanie Plageman
Subject Re: PG17 optimizations to vacuum
Date
Msg-id CAAKRu_aBthDxatwzR-wQ8bWfYehuxYgAO0g6AMPFyVgdOxfS4g@mail.gmail.com
Whole thread Raw
In response to Re: PG17 optimizations to vacuum  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: PG17 optimizations to vacuum
List pgsql-general
On Sun, Sep 1, 2024 at 6:00 PM Peter Geoghegan <pg@bowt.ie> wrote:
>
> On Sun, Sep 1, 2024 at 5:44 PM Pavel Luzanov <p.luzanov@postgrespro.ru> wrote:
> > I see a perfectly working TID-store optimization.
> > With reduced maintenance_work_mem it used only one 'vacuuming indexes'
> > phase instead of 21 in v16.
> > But I also expected to see a reduction in the number of WAL records
> > and the total size of the WAL. Instead, WAL numbers have significantly
> > degraded.
> >
> > What am I doing wrong?

I'll investigate more tomorrow, but based on my initial investigation,
there appears to be some interaction related to how much of the
relation is in shared buffers after creating the table and updating
it. If you set shared_buffers sufficiently high and prewarm the table
after the update, master has fewer WAL records reported by vacuum
verbose.

- Melanie



pgsql-general by date:

Previous
From: veem v
Date:
Subject: Re: Partitioning and unique key
Next
From: Peter Geoghegan
Date:
Subject: Re: PG17 optimizations to vacuum