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

From Martín Marqués
Subject Re: Read access for pg_monitor to pg_replication_origin_status view
Date
Msg-id CAPdiE1xchn=v3=r9b4FpE=CuDFaQivv+ogQk0NXsbyFY6y4QSA@mail.gmail.com
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
List pgsql-hackers
Hi Michael,

> Wouldn't it be just better to remove this hardcoded superuser check
> and replace it with equivalent ACLs by default?  The trick is to make
> sure that any function calling replorigin_check_prerequisites() has
> its execution correctly revoked from public.  See for example
> e79350fe.

Looking at that, it seems a better solution. Let me wrap up a new
patch, likely later today or early tomorrow as it's Sunday ;-)

--
Martín Marqués                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Andy Fan
Date:
Subject: A wrong index choose issue because of inaccurate statistics
Next
From: Vik Fearing
Date:
Subject: Compatible defaults for LEAD/LAG