From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: "CURRENT_ROLE" is not documented |
Date: | 2017-05-06 19:13:29 |
Message-ID: | alpine.DEB.2.20.1705062110160.3896@lancre |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> functions with the attribute <literal>SECURITY DEFINER</literal>.
> In Unix parlance, the session user is the <quote>real user</quote> and
> the current user is the <quote>effective user</quote>.
> + <function>current_role</function> and <function>user</function> are
> + synonyms for <function>current_user</function>. (The SQL standard draws
> + a distinction between <function>current_role</function>
> + and <function>current_user</function>, but <productname>PostgreSQL</>
> + does not, since it unifies users and roles into a single kind of entity.)
Looks simple and good to me. Thanks for the wording!
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2017-05-06 20:22:56 | MSVC odd TAP test problem |
Previous Message | Noah Misch | 2017-05-06 19:02:46 | Re: [BUGS] Concurrent ALTER SEQUENCE RESTART Regression |