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

From Pavel Luzanov
Subject Re: PG17 optimizations to vacuum
Date
Msg-id 7bc8da54-fe4f-4ff2-aa4e-b54fc91df586@postgrespro.ru
Whole thread Raw
In response to Re: PG17 optimizations to vacuum  (Melanie Plageman <melanieplageman@gmail.com>)
Responses Re: PG17 optimizations to vacuum
Re: PG17 optimizations to vacuum
List pgsql-general
On 02.09.2024 22:23, Melanie Plageman wrote:
For some reason I stopped being able to reproduce Pavel's case.
I repeated the test on another computer, but compared master with v15.
The results are the same. The test can be simplified as follows:

CREATE TABLE t(id integer) WITH (autovacuum_enabled = off);
INSERT INTO t SELECT gen.id FROM generate_series(1,3_500_000) gen(id);
CREATE INDEX t_id ON t(id);
VACUUM FREEZE t;
UPDATE t SET id = id + 1;
VACUUM FREEZE VERBOSE t;

My results (only line with WAL info from the last VACUUM command).

master:
WAL usage: 119583 records, 37231 full page images, 272631468 bytes

v15:
WAL usage: 96565 records, 47647 full page images, 217144602 bytes


If it helps, without creating index on id column, the numbers will be
much closer:

master:
WAL usage: 78502 records, 22090 full page images, 196215494 bytes

v15:
WAL usage: 77437 records, 30872 full page images, 152080268 bytes
-- 
Pavel Luzanov
Postgres Professional: https://postgrespro.com

pgsql-general by date:

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