From: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgbench --startup option |
Date: | 2013-02-10 23:45:19 |
Message-ID: | CAEYLb_Uv7kCgMqRCK4FZJJUcZt2Q0YxOEYQjD+LUfhaEAbW35A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10 February 2013 23:27, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> While looking at some proposed patches and pondering some questions on
> performance, I realized I desperately needed ways to run benchmarks with
> different settings without needing to edit postgresql.conf and
> restart/reload the server each time.
I'd thought about hacking this capability into pgbench-tools, so that
there was a new outer-most loop that iterates through different
postgresql.conf files. Come to think of it, the need to vary settings
per test set (that is, per series of benchmarks, each of which is
plotted as a different color) generally only exists for one or two
settings, so it is probably better to pursue the approach that you
propose here.
I guess what I've outlined could still be useful for PGC_POSTMASTER
gucs, like shared_buffers.
--
Regards,
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-02-10 23:47:30 | Re: BUG #7493: Postmaster messages unreadable in a Windows console |
Previous Message | Jeff Janes | 2013-02-10 23:27:49 | pgbench --startup option |