On Thu, 2009-05-07 at 12:47 -0400, Tom Lane wrote:
> Well, pgbench has been coded this way since forever and we've only seen
> this one report of trouble. Still, I can't object very hard to renaming
> the tables to pgbench_accounts etc --- it's a trivial change and the
> only thing it could break is custom pgbench scenarios that rely on the
> default scenario's tables, which there are probably not many of.
>
> So do we have consensus on dropping the "SET search_path" and renaming
> the tables?
+1 (I hate prefixed table names but I get the idea)
Joshua D. Drake
>
> regards, tom lane
>
--
PostgreSQL - XMPP: jdrake@jabber.postgresql.org Consulting, Development, Support, Training 503-667-4564 -
http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997