Re: Session Identifiers
От | Pavel Stehule |
---|---|
Тема | Re: Session Identifiers |
Дата | |
Msg-id | CAFj8pRBd68erVN7N50nMnOad2z_hAn2mK4D7orMHxAdLJ9HzEA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Session Identifiers (Dmitry Igrishin <dmitigr@gmail.com>) |
Ответы |
Re: Session Identifiers
|
Список | pgsql-general |
2015-12-20 17:30 GMT+01:00 Dmitry Igrishin <dmitigr@gmail.com>:
Can be totally different if you use some connection pooler like pgpool or pgbouncer - these applications can reuse Postgres server sessions for more user sessions.BTW, AFAIK, it's not possible to change the session authentication information byusing SET SESSION AUTHORIZATION [1] if the current user is not a superuser.But it would be very nice to have a feature to change the session authorizationof current user even without superuser's privilege by supplying a password ofthe user specified in SET SESSION AUTHORIZATION. This feature allowsto use PostgreSQL's native privileges via connection pools -- i.e. withoutneeds to open a dedicated connection for authenticated user. Is it possibleto implement it?
there is a workaround with security definer function and SET role TO ?
Pavel
В списке pgsql-general по дате отправления: