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 20200610033549.GH38342@paquier.xyz
Whole thread Raw
In response to Re: Read access for pg_monitor to pg_replication_origin_status view  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
Responses Re: Read access for pg_monitor to pg_replication_origin_status view  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Tue, Jun 09, 2020 at 05:07:39PM +0900, Masahiko Sawada wrote:
> Oh, I see. There might be room for improvement but it's a separate issue.
>
> 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.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: "Andrey V. Lepikhov"
Date:
Subject: Re: Global snapshots
Next
From: Fujii Masao
Date:
Subject: Re: FailedAssertion at ReorderBufferCheckMemoryLimit()