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

From Robert Haas
Subject Re: [v9.2] Add GUC sepgsql.client_label
Date
Msg-id CA+TgmoYWEGrvoSU+HnzCSbjaXDwe1qrEE3QLSfGG3HLize-hyg@mail.gmail.com
Whole thread Raw
In response to Re: [v9.2] Add GUC sepgsql.client_label  (Yeb Havinga <yebhavinga@gmail.com>)
Responses Re: [v9.2] Add GUC sepgsql.client_label  (Yeb Havinga <yebhavinga@gmail.com>)
List pgsql-hackers
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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [GENERAL] pg_dump -s dumps data?!
Next
From: Robert Haas
Date:
Subject: Re: foreign key locks, 2nd attempt