Re: invalid search_path complaints

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Christoph Berg <cb(at)df7cb(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: invalid search_path complaints
Date: 2012-04-11 01:37:06
Message-ID: 2137.1334108226@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Apr 10, 2012 at 7:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Anyway, if you're happy with 9.1 being an outlier on this behavior,
>> I won't press the point.

> I'm not, particularly.

Well, the other thing we could do is tweak the rules for when to print a
complaint. I notice that in check_temp_tablespaces we use the rule

source == PGC_S_SESSION (ie, SET) -> error
source == PGC_S_TEST (testing value for ALTER SET) -> notice
else -> silently ignore bad name

which seems like it could be applied to search_path without giving
anyone grounds for complaint. I'm still in favor of the previous patch
for HEAD, but maybe we could do this in 9.1.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-04-11 02:04:24 Re: Last gasp
Previous Message Jeff Janes 2012-04-11 01:33:35 Re: Last gasp