Re: Reverting SET SESSION AUTHORIZATION command - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Reverting SET SESSION AUTHORIZATION command
Date
Msg-id Pine.LNX.4.30.0203102040030.684-100000@peter.localdomain
Whole thread Raw
In response to Re: Reverting SET SESSION AUTHORIZATION command  (Fernando Nasser <fnasser@redhat.com>)
List pgsql-hackers
Fernando Nasser writes:

> The SQL standard has already defined what should go there.
> That would be CURRENT_USER, so you would have:
>
> SET SESSION AUTHORIZATION CURRENT_USER

I don't think so.  SET SESSION AUTHORIZATON sets the current user, so the
identity of the original current user is lost (or at least it's not
available through the CURRENT_USER function).

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Uniqueness of rule, constraint, and trigger names
Next
From: Thomas Lockhart
Date:
Subject: Re: Uniqueness of rule, constraint, and trigger names