| From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | pg(at)bowt(dot)ie |
| Cc: | coelho(at)cri(dot)ensmp(dot)fr, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Using COPY FREEZE in pgbench |
| Date: | 2021-04-02 23:58:41 |
| Message-ID: | 20210403.085841.1757025420600032778.t-ishii@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhihong Yu | 2021-04-03 00:07:27 | Re: Have I found an interval arithmetic bug? |
| Previous Message | Bruce Momjian | 2021-04-02 23:58:15 | Re: Have I found an interval arithmetic bug? |