Re: Using COPY FREEZE in pgbench
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-04-02T22:55:54Z
Lists: pgsql-hackers
On Sun, Mar 21, 2021 at 5:23 PM Tatsuo Ishii <ishii@sraoss.co.jp> wrote: > Anyway, this time total pgbench time is reduced by 14% over all > here. I hope people agree that the patch is worth the gain. Most of the time when I run pgbench I use my own shell script, which does this: PGOPTIONS='-c vacuum_freeze_min_age=0 -c wal_compression=off' pgbench -i -s $SCALE Have you considered this case? In other words, have you considered the benefits of this patch for users that currently deliberately force freezing by VACUUM, just because it matters to their benchmark? (BTW you might be surprised how much wal_compression=off matters here.) -- Peter Geoghegan
Commits
-
Use COPY FREEZE in pgbench for faster benchmark table population.
- 06ba4a63b85e 15.0 landed
-
Revert most of 39b66a91bd
- 8e03eb92e9ad 14.0 cited
-
Set PD_ALL_VISIBLE and visibility map bits in COPY FREEZE
- 7db0cd2145f2 14.0 cited