Greg Smith <[email protected]> writes:
> On Thu, 7 May 2009, Aidan Van Dyk wrote:
> You are correct here. Right now, pgbench is guaranteed to be running
> against a search_path with only one entry in it. If someone runs the new
> version against a configuration with something like:
> search_path='a,b,c,d,e,f,g,h,i,j,public'
> instead, that is going to execute more slowly than the current pgbench
> would have.
No, it is not. The tables will be created and used in schema 'a',
and the effective search path depth will be the same.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
