From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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: | 2015-04-30 20:02:16 |
Message-ID: | CA+TgmoZkOH6gj8y+BGaK2FNFp1GATN63z8+sqAFD7afE5Qi+ew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 11, 2015 at 2:00 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> But as far as what has been discussed on the central topic of this thread, I
> think that doing the vacuum and making the failure for non-existent tables
> be non-fatal when -f is provided would be an improvement. Or maybe just
> making it non-fatal at all times--if the table is needed and not present,
> the session will fail quite soon anyway. I don't see the other changes as
> being improvements. I would rather just learn to add the -n when I use -f
> and don't have the default tables in place, than have to learn new methods
> for saying "no really, I left -n off on purpose" when I have a custom file
> which does use the default tables and I want them vacuumed.
So, discussion seems to have died off here. I think what Jeff is
proposing here is a reasonable compromise. Patch for that attached.
Objections?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment | Content-Type | Size |
---|---|---|
pgbench-vacuum-failure-not-fatal.patch | binary/octet-stream | 1.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-04-30 20:12:25 | Re: alter user/role CURRENT_USER |
Previous Message | Tom Lane | 2015-04-30 20:02:13 | Re: EvalPlanQual behaves oddly for FDW queries involving system columns |