| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Dickson S(dot) Guedes" <listas(at)guedesoft(dot)net>, Greg Smith <gsmith(at)gregsmith(dot)com>, jd(at)commandprompt(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Patch to fix search_path defencies with pg_bench |
| Date: | 2009-05-07 15:29:32 |
| Message-ID: | 1241710172.6109.235.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2009-05-07 at 11:14 -0400, Robert Haas wrote:
> > We should check they are the correct tables before we just drop them.
> > Perhaps check for the comment "Tables for pgbench application. Not
> > production data" on the tables, which would be nice to add anyway.
>
> I bet it would be just as good and a lot simpler to do what someone
> suggested upthread, namely s/^/pgbench_/
Running pgbench has become more popular now, with various people
recommending running it on every system to test performance. I don't
disagree with that recommendation, but I've had problems myself with a
similar issue - hence earlier patch to prevent pgbench running a
complete database VACUUM before every test run.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-05-07 15:56:48 | Re: Serializable Isolation without blocking |
| Previous Message | Kevin Grittner | 2009-05-07 15:16:00 | Re: Serializable Isolation without blocking |