Re: [v9.2] Add GUC sepgsql.client_label - Mailing list pgsql-hackers

From Yeb Havinga
Subject Re: [v9.2] Add GUC sepgsql.client_label
Date
Msg-id 4F27F65B.7020801@gmail.com
Whole thread Raw
In response to Re: [v9.2] Add GUC sepgsql.client_label  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [v9.2] Add GUC sepgsql.client_label
List pgsql-hackers
On 2012-01-31 14:06, Robert Haas wrote:
> On Tue, Jan 31, 2012 at 4:36 AM, Yeb Havinga<yebhavinga@gmail.com>  wrote:
>> What about always allowing a transition to the default / postgresql.conf
>> configured client label, so in the case of errors, or RESET, the transition
>> to this domain is hardcoded to succeed. This would also be useful in
>> conjunction with a connection pooler. This would still allow the option to
>> prevent a back transition to non-default client labels.
> I don't think you can make that work, because someone can still
> attempt to RESET to a different value, and it's still not safe to make
> that fail.

But the idea is that if that different value is a (possibly changed into 
a new) allowed default value, a RESET to that new default value will be 
allowed, by definition, because it is a default value.


-- 
Yeb Havinga
http://www.mgrid.net/
Mastering Medical Data



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: patch for parallel pg_dump
Next
From: Robert Haas
Date:
Subject: Re: Group commit, revised