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

From Peter Geoghegan
Subject Re: PG17 optimizations to vacuum
Date
Msg-id CAH2-WzkuMLJxf+s-YzYnsu=7g3HuP9+YAV1vy_yAi2R17cdj-Q@mail.gmail.com
Whole thread Raw
In response to Re: PG17 optimizations to vacuum  (Melanie Plageman <melanieplageman@gmail.com>)
List pgsql-general
On Mon, Sep 2, 2024 at 3:23 PM Melanie Plageman
<melanieplageman@gmail.com> 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



pgsql-general by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: PG17 optimizations to vacuum
Next
From: Laurenz Albe
Date:
Subject: Re: Partitioning and unique key