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

From Aidan Van Dyk
Subject Re: Patch to fix search_path defencies with pg_bench
Date
Msg-id 20090507170535.GH3305@yugib.highrise.ca
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
* Joshua D. Drake <jd@commandprompt.com> [090507 13:02]:
> 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.

Sure, but by putting a sane default (which seems to be leaning towards
"" or "pgbench_"), you don't *need* to do anything on the command line.

> > 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.

Well ya, but at least you didn't have any pgbench result to try and
"compare unevenly" with something else ;-)

a.

-- 
Aidan Van Dyk                                             Create like a god,
aidan@highrise.ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.

pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Patch to fix search_path defencies with pg_bench
Next
From: Simon Riggs
Date:
Subject: Re: Patch to fix search_path defencies with pg_bench