Re: Using COPY FREEZE in pgbench - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Using COPY FREEZE in pgbench
Date
Msg-id CAH2-WzndCO4Ri6gj1N6fLV6OiabedxtQZjeZ0VrP2hiL5X2ycQ@mail.gmail.com
Whole thread Raw
In response to Re: Using COPY FREEZE in pgbench  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Responses Re: Using COPY FREEZE in pgbench  (Tatsuo Ishii <ishii@sraoss.co.jp>)
List 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



pgsql-hackers by date:

Previous
From: Dan Lynch
Date:
Subject: Re: policies with security definer option for allowing inline optimization
Next
From: Tom Lane
Date:
Subject: Re: libpq debug log