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

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <robertmhaas(at)gmail(dot)com>,<yebhavinga(at)gmail(dot)com>, <kaigai(at)kaigai(dot)gr(dot)jp>, <pgsql-hackers(at)postgresql(dot)org>, <jbrindle(at)tresys(dot)com>
Subject: Re: [v9.2] Add GUC sepgsql.client_label
Date: 2012-02-04 19:24:33
Message-ID: 4F2D31910200002500044DBF@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

> What I was concerned about was the case where GUC is trying to
> re-establish an old value during transaction rollback. For example,
> assume we are superuser to start with, and we do
>
> begin;
> set role unprivileged_user;
> ...
> rollback;
>
> The rollback needs to transition the role setting back to
> superuser.

Sorry for missing the point. Yeah, I totally agree with that.

> And yeah, I agree it's a bug that you can do what Kevin's example
> shows.

I'll look at it and see if I can pull together a patch.

-Kevin

Browse pgsql-hackers by date

  From Date Subject
Next Message Bridget Frey 2012-02-04 19:52:09 Re: BUG #6425: Bus error in slot_deform_tuple
Previous Message Jeff Janes 2012-02-04 19:13:45 Re: some longer, larger pgbench tests with various performance-related patches