Re: Patch to fix search_path defencies with pg_bench - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Patch to fix search_path defencies with pg_bench
Date
Msg-id 1241716068.6109.291.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Patch to fix search_path defencies with pg_bench  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
On Thu, 2009-05-07 at 09:53 -0700, Joshua D. Drake wrote:
> 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)

+1, sorry JD.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Aidan Van Dyk
Date:
Subject: Re: Patch to fix search_path defencies with pg_bench
Next
From: Tom Lane
Date:
Subject: Re: Patch to fix search_path defencies with pg_bench