Re: [v9.2] Add GUC sepgsql.client_label

Yeb Havinga <yebhavinga@gmail.com>

View thread

From: Yeb Havinga <yebhavinga@gmail.com>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Kohei KaiGai <kaigai@kaigai.gr.jp>, PgHacker <pgsql-hackers@postgresql.org>, Joshua Brindle <jbrindle@tresys.com>

Date: 2012-03-11T10:33:57Z

Lists: pgsql-hackers

Attachments

pgsql-v9.2-sepgsql-setcon.part2-v5.patch (text/x-patch) patch v9

On 2012-03-10 10:39, I  wrote:
>
> I can probably write some docs tomorrow.
>

Attached is v5 of the patch, with is exactly equal to v4 but with added 
documentation.

Some other notes.

- Robert asked why sepgsql_setcon with NULL to reset the value to the 
initial client label was supported. Maybe this could be a leftover from 
the initial implementation as GUC variable?
- earlier I suggested preventing setting a new client label from a 
trusted procedure, however I just read in the original post that this 
was how the current usecase of Joshua is set up. Suggestion withdrawn.

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