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

From Joshua D. Drake
Subject Re: Patch to fix search_path defencies with pg_bench
Date
Msg-id 1241715717.11534.44.camel@jd-laptop.pragmaticzealot.org
Whole thread Raw
In response to Re: Patch to fix search_path defencies with pg_bench  (Aidan Van Dyk <aidan@highrise.ca>)
Responses Re: Patch to fix search_path defencies with pg_bench  (Aidan Van Dyk <aidan@highrise.ca>)
Re: Patch to fix search_path defencies with pg_bench  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 2009-05-07 at 12:58 -0400, Aidan Van Dyk wrote:

> True enough... What about making the prefix be configurable, so by
> default, it could be "pgbench_", it could be set to "" (to force it to
> use old pgbench names) or set to "something." to get it to use a
> different schema (noting that the comparisons to older ones not doing
> catalog lookups are void).

Then you have to pass the prefix on the command line. That seems a bit
over doing it for such a simple utility.

> 
> But by dropping the search_path, you're necessarily changing the catalog
> comparisons and lookups anyways, because your now taking a "random"
> search path to follow (which could have multiple entries in it) instead
> of one guaranteed to be a single, useable entry.

Except that it isn't a guaranteed usable entry, which is why I submitted
the patch.

Sincerely,

Joshua D. Drake

-- 
PostgreSQL - XMPP: jdrake@jabber.postgresql.org  Consulting, Development, Support, Training  503-667-4564 -
http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997
 



pgsql-hackers by date:

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