From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, Tomáš Vondra <tv(at)fuzzy(dot)cz>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgbench -f and vacuum |
Date: | 2014-12-23 14:40:21 |
Message-ID: | CA+TgmoaV32PJB+-Oi8tvAq6hhP_YoTL6795BWLKatGr_didJ+Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Dec 22, 2014 at 6:55 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Here's a completely different idea. How about we add an option that
> means "vacuum this table before running the test" (can be given several
> times); by default the set of vacuumed tables is the current pgbench_*
> list, but if -f is specified then the default set is cleared. So if you
> have a -f script and want to vacuum the default tables, you're forced to
> give a few --vacuum-table=foo options. But this gives the option to
> vacuum some other table before the test, not just the pgbench default
> ones.
Well, really, you might want arbitrary initialization steps, not just
vacuums. We could have --init-script=FILENAME. Although that might
be taking this thread rather far off-topic.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Fabrízio de Royes Mello | 2014-12-23 14:54:01 | Re: Proposal "VACUUM SCHEMA" |
Previous Message | Tomas Vondra | 2014-12-23 14:32:59 | Re: Initdb-cs_CZ.WIN-1250 buildfarm failures |