From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: "is_superuser" parameter creates inconsistencies |
Date: | 2003-08-31 04:05:59 |
Message-ID: | 200308310405.h7V45xR09469@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Presumably, the "is_superuser" parameter was intended to make the updating
> > of psql's prompt more accurate when SET SESSION AUTHORIZATION is used.
> > However, if the prompt is customized to include the user name (%n), then
> > the prompt changes to reflect the real superuser status, but does not
> > change the user name. I guess we need to pass "session_user" as well.
>
> Seems reasonable. IIRC the only addition needed to the server code is
> to set a flag in the variable's GUC entry.
Is this a TODO item or something we want to address for 7.4?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-08-31 04:26:29 | Re: pg_dump and REVOKE on function |
Previous Message | Stephan Szabo | 2003-08-31 02:30:16 | Re: Is it a memory leak in PostgreSQL 7.4beta? |