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

From Tom Lane
Subject Re: Read access for pg_monitor to pg_replication_origin_status view
Date
Msg-id 1098356.1592196242@sss.pgh.pa.us
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  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> On Wed, Jun 10, 2020 at 12:35:49PM +0900, Michael Paquier wrote:
>> 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.

FWIW, I'd have included a catversion bump in this, to enforce that
the modified backend functions are used with matching pg_proc entries.
It's not terribly important at this phase of the devel cycle, but still
somebody might wonder why the regression tests are failing for them
(if they tried to skip an initdb).

            regards, tom lane



pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Review for GetWALAvailability()
Next
From: Michael Paquier
Date:
Subject: Re: min_safe_lsn column in pg_replication_slots view