Re: Using COPY FREEZE in pgbench

Tatsuo Ishii <ishii@sraoss.co.jp>

From: Tatsuo Ishii <ishii@sraoss.co.jp>
To: pg@bowt.ie
Cc: coelho@cri.ensmp.fr, pgsql-hackers@lists.postgresql.org
Date: 2021-04-02T23:58:41Z
Lists: pgsql-hackers
> 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?

I am not sure how many people use this kind of options while running
pgbench -i but we could add yet another switch to fall back to none
FREEZE COPY if you want.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



Commits

  1. Use COPY FREEZE in pgbench for faster benchmark table population.

  2. Revert most of 39b66a91bd

  3. Set PD_ALL_VISIBLE and visibility map bits in COPY FREEZE