| From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgbench - implement strict TPC-B benchmark |
| Date: | 2019-08-27 15:26:49 |
| Message-ID: | CA+q6zcUBhD3b4fnF94+=8h577Xn8kCFgqg8+2xn_=+6F-A=bLw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Mon, Aug 5, 2019 at 10:46 PM Fabien COELHO <coelho(at)cri(dot)ensmp(dot)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 | Content-Type | Size |
|---|---|---|
| v1-0001-pgbench-load-options.patch | application/octet-stream | 3.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul A Jungwirth | 2019-08-27 15:52:33 | Re: range bug in resolve_generic_type? |
| Previous Message | Tom Lane | 2019-08-27 15:23:32 | Re: range bug in resolve_generic_type? |