Re: SET SESSION AUTHORIZATION command doesn't update status of backend

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: SET SESSION AUTHORIZATION command doesn't update status of backend
Дата
Msg-id 952987.1634305805@sss.pgh.pa.us
обсуждение исходный текст
Ответ на SET SESSION AUTHORIZATION command doesn't update status of backend  ("Andrey V. Lepikhov" <a.lepikhov@postgrespro.ru>)
Ответы Re: SET SESSION AUTHORIZATION command doesn't update status of backend  (Andrey Lepikhov <a.lepikhov@postgrespro.ru>)
Список pgsql-bugs
Дерево обсуждения 
"Andrey V. Lepikhov" <a.lepikhov@postgrespro.ru> writes:
> Nikita Degtyarev (n.degtyarev@postgrespro.ru) reported a suspicious 
> behaviour of a SET SESSION AUTHORIZATION command. If you switch user in 
> a session:
> [ pg_stat_activity doesn't change ]

I don't think this is a bug.  pg_stat_activity is reporting the session's
login identity, and that seems fine, though maybe the documentation about
it needs to be clarified.

            regards, tom lane

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

Предыдущее
От: "Andrey V. Lepikhov"
Дата:
Сообщение: SET SESSION AUTHORIZATION command doesn't update status of backend
Следующее
От: PG Bug reporting form
Дата:
Сообщение: BUG #17231: ERROR: tuple concurrently updated