Greg Smith <gsm...@gregsmith.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". I doubt that either adding or removing the "set search_path"
command changes the risk of trouble very much.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
