| From: | "Dickson S(dot) Guedes" <listas(at)guedesoft(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-06 18:53:10 |
| Message-ID: | 1241635990.4141.21.camel@analise3.cresoltec.com.br |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Em Qua, 2009-05-06 às 09:37 -0400, Tom Lane escreveu:
> Greg Smith <gsmith(at)gregsmith(dot)com> writes:
> > I once did some pgbench testing on a system that included a real
> > "accounts" table in a named schema. "pgbench -i" will execute "drop table
> > if exists accounts". It had already accidentally wiped out the copy of
> > the accounts table on the system during an earlier test, before the schema
> > policy was in place, leaving everyone wary of it.
>
> Seems like the right policy for that is "run pgbench in its own
> database".
A text warning about this could be shown at start of pgbench if the
target database isn't named "pgbench", for examplo, or just some text
could be added to the docs.
regards.
--
Dickson S. Guedes
mail/xmpp: guedes(at)guedesoft(dot)net - skype: guediz
http://guedesoft.net - http://planeta.postgresql.org.br
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2009-05-06 18:58:57 | lazy vacuum blocks analyze |
| Previous Message | Stephen Frost | 2009-05-06 18:31:03 | Re: text_pattern_ops and complex regexps |