Re: "is_superuser" parameter creates inconsistencies

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: "is_superuser" parameter creates inconsistencies
Дата
Msg-id Pine.LNX.4.44.0308312103080.1119-100000@peter.localdomain
обсуждение исходный текст
Ответ на Re: "is_superuser" parameter creates inconsistencies  (Bruce Momjian <pgman@candle.pha.pa.us>)
Ответы Re: "is_superuser" parameter creates inconsistencies  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Bruce Momjian writes:

> Tom Lane wrote:
> > Peter Eisentraut <peter_e@gmx.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@gmx.net



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: pgAdmin III translation: Dutch
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: Passing server_encoding to the client is not future-proof