Re: Using COPY FREEZE in pgbench

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: coelho(at)cri(dot)ensmp(dot)fr
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Using COPY FREEZE in pgbench
Date: 2021-03-21 09:30:59
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> The feature is a little disappointing because if someone has partition
> tables then probably they have a lot of data and probably they would
> like freeze to work there. Maybe freeze would work on table partitions
> themselves, but I do not think it is worth the effort to do that.


> About v4 there is a typo in the doc "portioning":
> <command>pgbench</command> uses FREEZE option with 14 or later
> version of <productname>PostgreSQL</productname> to speed up
> subsequent <command>VACUUM</command> if portioning option is not
> specified.
> I'd suggest:
> <command>pgbench</command> uses the FREEZE option with 14 or later
> version of <productname>PostgreSQL</productname> to speed up
> subsequent <command>VACUUM</command>, unless partitions are enabled.

Thanks for pointing it out. Also I think that in "with 14 or later
version", "version" should be "versions".

Attached is the v5 patch.

Best regards,
Tatsuo Ishii
SRA OSS, Inc. Japan

Attachment Content-Type Size
pgbench_freeze_v5.diff text/x-patch 2.0 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2021-03-21 09:37:36 Re: proposal - psql - use pager for \watch command
Previous Message Gilles Darold 2021-03-21 09:21:17 Re: [PATCH] proposal for regexp_count, regexp_instr, regexp_substr and regexp_replace