From: | Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> |
---|---|
To: | Melanie Plageman <melanieplageman(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
Subject: | Re: PG17 optimizations to vacuum |
Date: | 2024-09-02 20:35:04 |
Message-ID: | 7bc8da54-fe4f-4ff2-aa4e-b54fc91df586@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2024-09-02 20:58:25 | Re: PG17 optimizations to vacuum |
Previous Message | Laurenz Albe | 2024-09-02 19:44:37 | Re: Partitioning and unique key |