Re: pgbench - implement strict TPC-B benchmark - Mailing list pgsql-hackers

From Dmitry Dolgov
Subject Re: pgbench - implement strict TPC-B benchmark
Date
Msg-id CA+q6zcUBhD3b4fnF94+=8h577Xn8kCFgqg8+2xn_=+6F-A=bLw@mail.gmail.com
Whole thread Raw
In response to Re: pgbench - implement strict TPC-B benchmark  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: pgbench - implement strict TPC-B benchmark  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
> On Mon, Aug 5, 2019 at 10:46 PM Fabien COELHO <coelho@cri.ensmp.fr> wrote:
>
> > The index builds are done serially. The vacuum could be replaced by COPY
> > FREEZE.
>
> Well, it could be added?

While doing benchmarking using different tools, including pgbench, I found it
useful as a temporary hack to add copy freeze and maintenance_work_mem options
(the last one not as an env variable, just as a set before, although not sure
if it's a best idea). Is it similar to what you were talking about?

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: range bug in resolve_generic_type?
Next
From: Paul A Jungwirth
Date:
Subject: Re: range bug in resolve_generic_type?