From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)postgresql(dot)org> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql/ oc/src/sgml/ref/set_session_auth.sgml r ... |
Date: | 2002-05-10 19:16:51 |
Message-ID: | Pine.LNX.4.44.0205102114100.5390-100000@localhost.localdomain |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Tom Lane writes:
> Accept SET SESSION AUTHORIZATION DEFAULT and RESET SESSION AUTHORIZATION
> to reset session userid to the originally-authenticated name. Also,
> relax SET SESSION AUTHORIZATION to allow specifying one's own username
> even if one is not superuser, so as to avoid unnecessary error messages
> when loading a pg_dump file that uses this command. Per discussion from
> several months ago.
I noticed you added SHOW SESSION AUTHORIZATION here as showing the
SESSION_USER. I don't think this makes sense, because SET SESSION
AUTHORIZATION is not the same as setting the session user only. Also, in
response to your comment, no, I don't think RESET all should reset the
session user. I think it would be better to treat SET SESSION
AUTHORIZATION separately from the other SET commands, since it behaves
differently in effect and privileges.
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-05-10 19:23:11 | Re: pgsql/ oc/src/sgml/ref/set_session_auth.sgml r ... |
Previous Message | Peter Eisentraut - PostgreSQL | 2002-05-09 13:30:24 | pgsql/ oc/src/sgml/runtime.sgml rc/backend/acc ... |