public inbox for [email protected]  

help / color / mirror / Atom feed

From: Melanie Plageman <[email protected]>
To: Peter Geoghegan <[email protected]>
Cc: Pavel Luzanov <[email protected]>
Cc: pgsql-generallists.postgresql.org <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Subject: Re: PG17 optimizations to vacuum
Date: Mon, 2 Sep 2024 13:28:49 -0400
Message-ID: <CAAKRu_aBthDxatwzR-wQ8bWfYehuxYgAO0g6AMPFyVgdOxfS4g@mail.gmail.com> (raw)
In-Reply-To: <CAH2-Wz=pCtsB3v42RB5dLnzEn3tQLUJ8fJMn+si-9A8s6v=B1A@mail.gmail.com>
References: <[email protected]>
	<CAH2-Wz=pCtsB3v42RB5dLnzEn3tQLUJ8fJMn+si-9A8s6v=B1A@mail.gmail.com>

On Sun, Sep 1, 2024 at 6:00 PM Peter Geoghegan <[email protected]> wrote:
>
> On Sun, Sep 1, 2024 at 5:44 PM Pavel Luzanov <[email protected]> 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

view thread (2+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: PG17 optimizations to vacuum
  In-Reply-To: <CAAKRu_aBthDxatwzR-wQ8bWfYehuxYgAO0g6AMPFyVgdOxfS4g@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox