From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: "is_superuser" parameter creates inconsistencies |
Date: | 2003-08-31 19:03:58 |
Message-ID: | Pine.LNX.4.44.0308312103080.1119-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian writes:
> 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?
I'd like to address it for 7.4, but it looks a bit more difficult than it
seemed at first, because session_user isn't in GUC at all, so there is no
infrastructure to pass it to the client.
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-08-31 19:06:17 | Re: Passing server_encoding to the client is not future-proof |
Previous Message | Peter Eisentraut | 2003-08-31 18:51:24 | Re: pgAdmin III translation: Dutch |