public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Geoghegan <[email protected]>
To: Melanie Plageman <[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 15:42:00 -0400
Message-ID: <CAH2-WzkuMLJxf+s-YzYnsu=7g3HuP9+YAV1vy_yAi2R17cdj-Q@mail.gmail.com> (raw)
In-Reply-To: <CAAKRu_YF9UeFnfsgDiFybAss2YQtmEHU+xjngqwmwwyQjCDvxQ@mail.gmail.com>
References: <[email protected]>
<CAH2-Wz=pCtsB3v42RB5dLnzEn3tQLUJ8fJMn+si-9A8s6v=B1A@mail.gmail.com>
<CAAKRu_aBthDxatwzR-wQ8bWfYehuxYgAO0g6AMPFyVgdOxfS4g@mail.gmail.com>
<CAH2-Wznqbnc8en8+B26obp-pmTKXi_HS_h_yRt4HVtqLOCKxLQ@mail.gmail.com>
<CAAKRu_YF9UeFnfsgDiFybAss2YQtmEHU+xjngqwmwwyQjCDvxQ@mail.gmail.com>
On Mon, Sep 2, 2024 at 3:23 PM Melanie Plageman
<[email protected]> wrote:
> This is roughly what I get for records by vacuum. Note that I prefixed
> VACUUM with BTREE on master to indicate those records are from index
> vacuuming. By default the headesc routine for records emitted by index
> vacuuming prints just VACUUM -- perhaps it would be better to prefix
> it.
>
> Note that these add up to almost the same thing. I don't know yet why
> the number PRUNE_VACUUM_SCAN is different than PRUNE on 16.
That is indeed surprising, given that Pavel's VACUUM VERBOSE output
indicates that the number of heap tuples deleted is identical across
versions. The output also strongly suggests that the same heap pages
are pruned on both versions, since the "index scan needed: " line is
also identical across versions.
Might it be that the extra PRUNE_VACUUM_SCAN records originated in
pages that only contained existing LP_UNUSED items when scanned by
VACUUM?
--
Peter Geoghegan
view thread (7+ messages) latest in thread
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: <CAH2-WzkuMLJxf+s-YzYnsu=7g3HuP9+YAV1vy_yAi2R17cdj-Q@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