Re: Read access for pg_monitor to pg_replication_origin_status view - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Read access for pg_monitor to pg_replication_origin_status view
Date
Msg-id 20200614034540.GB1496@paquier.xyz
Whole thread Raw
In response to Re: Read access for pg_monitor to pg_replication_origin_status view  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Read access for pg_monitor to pg_replication_origin_status view  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Read access for pg_monitor to pg_replication_origin_status view  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
On Wed, Jun 10, 2020 at 12:35:49PM +0900, Michael Paquier wrote:
> On Tue, Jun 09, 2020 at 05:07:39PM +0900, Masahiko Sawada wrote:
>> I agreed with the change you proposed.
>
> OK, thanks.  Then let's wait a couple of days to see if anybody has
> any objections with the removal of the hardcoded superuser check
> for those functions.

Committed the part removing the superuser checks as of cc07264.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Add tap test for --extra-float-digits option
Next
From: Peter Eisentraut
Date:
Subject: Re: some grammar refactoring