Re: BUG #9136: pg_is_xlog_replay_paused() should not need Superuser

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: sys-milan(at)statpro(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #9136: pg_is_xlog_replay_paused() should not need Superuser
Date: 2014-04-17 00:02:06
Message-ID: 20140417000206.GV7443@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Feb 7, 2014 at 10:16:36AM +0000, sys-milan(at)statpro(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 9136
> Logged by: Renato Ramonda
> Email address: sys-milan(at)statpro(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message 德哥 2014-04-17 00:16:08 Re: BUG #10013: PostgreSQL 9.4 initdb FATAL: could not write to file "pg_xlog/xlogtemp.3590": No space left on devi
Previous Message Bruce Momjian 2014-04-16 23:05:26 Re: BUG #9046: vacuum analyze fails on a table that has domain that is a date rage