Re: Proposal to sync SET ROLE and pg_stat_activity
От | Alvaro Herrera |
---|---|
Тема | Re: Proposal to sync SET ROLE and pg_stat_activity |
Дата | |
Msg-id | 20080828155341.GE8424@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: Proposal to sync SET ROLE and pg_stat_activity (Grant Finnemore <grant@guruhut.com>) |
Ответы |
Re: Proposal to sync SET ROLE and pg_stat_activity
|
Список | pgsql-hackers |
Grant Finnemore wrote: > Well, pg_stat_activity isn't really the problem here, because as you > point out, it's just a view, and I could certainly redefine the view. > The limiting factor is that the backend doesn't push the role name > changes to the stats subsystem for either SET ROLE or SET SESSION > AUTH. Keep in mind that stats are updated only once every 500 ms, and messages have a nontrivial overhead. With your proposed changes, there would be a significant performance overhead to running security definer functions. A possible solution to this would be to publish current_user in shared memory, so that remote processes could read it from there (similar to how current_query is published). -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
В списке pgsql-hackers по дате отправления: