Re: BUG #9136: pg_is_xlog_replay_paused() should not need Superuser
От | Bruce Momjian |
---|---|
Тема | Re: BUG #9136: pg_is_xlog_replay_paused() should not need Superuser |
Дата | |
Msg-id | 20140417000206.GV7443@momjian.us обсуждение исходный текст |
Ответ на | BUG #9136: pg_is_xlog_replay_paused() should not need Superuser (sys-milan@statpro.com) |
Ответы |
Re: BUG #9136: pg_is_xlog_replay_paused() should not need Superuser
|
Список | pgsql-bugs |
On Fri, Feb 7, 2014 at 10:16:36AM +0000, sys-milan@statpro.com wrote: > The following bug has been logged on the website: > > Bug reference: 9136 > Logged by: Renato Ramonda > Email address: sys-milan@statpro.com > PostgreSQL version: 9.2.6 > Operating system: Ubuntu 12.04 > Description: > > The admin function pg_is_xlog_replay_paused() is read only and can be useful > for monitoring, as such it should NOT require superuser privileges (as it > does now). > > For reference, the read-only functions for monitoring the replication delay > such as pg_current_xlog_location can be executed without superuser > privileges (as remarked by the official documentation here > http://www.postgresql.org/docs/9.1/static/functions-admin.html ) Is this correct? Do we have proper super-user restrictions on all the right fields now? -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. +
В списке pgsql-bugs по дате отправления: