Re: [HACKERS] SESSION_USER

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: [HACKERS] SESSION_USER
Дата
Msg-id
4562.955747814@sss.pgh.pa.us
Ответ на
SESSION_USER (Bruce Momjian)
Список
Дерево обсуждения
SESSION_USER Bruce Momjian <pgman@candle.pha.pa.us>
Re: [HACKERS] SESSION_USER Tom Lane <tgl@sss.pgh.pa.us>
Re: Re: [HACKERS] SESSION_USER Peter Eisentraut <peter_e@gmx.net>
Re: Re: [HACKERS] SESSION_USER Bruce Momjian <pgman@candle.pha.pa.us>
Re: Re: [HACKERS] SESSION_USER Tom Lane <tgl@sss.pgh.pa.us>
Re: Re: [HACKERS] SESSION_USER Bruce Momjian <pgman@candle.pha.pa.us>
Bruce Momjian  writes:
> create_table.sgml mentions SESSION_USER is not supported.  I don't think
> that is true anymore, is it?

regression=# select session_user;
 getpgusername
---------------
 postgres
(1 row)

Looking at the spec, we do seem to be missing SYSTEM_USER out of the
four variants the spec mentions.  However, considering that we map
them all to the same thing anyway, I can't get too excited about it.

If something is done about making functions have setuid-like behavior,
we'd want to make sure that the appropriate ones of these functions
change value inside a function.

			regards, tom lane
В списке pgsql-docs по дате отправления
От: Bruce Momjian
Дата:
Сообщение: SESSION_USER
От: Bruce Momjian
Дата:
Сообщение: Doc TODO list is done
FAQ