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 CABeG9LtEw9w-YptGAMDvYK4oyXv2GC673gvHr=pWwprDHDLpfQ@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>)
List pgsql-hackers
Hello,

I wanted to resurface this thread.

The original intention I had with this patch I sent over a year ago
was to have the possibility for monitoring ROLEs like pg_monitor and
pg_read_all_stats to have read access for the replication origin
status. Seems the patch only got half way through (we removed the
superuser hardcoded restriction).

Too bad I didn't notice this until 14 got out, or I'd have done this
much earlier. Well, maybe it's time to do it now :)

Sending a patch to change the privileges of the on the view and
function called by the view.

The only thing I'm not sure, but can amend, is if we need tests for
this change (that would be something like switching ROLE to
pg_read_all_stats and query the pg_replication_origin_status, checking
we get the right result.

Kind regards, Martín

--
Martín Marqués
It’s not that I have something to hide,
it’s that I have nothing I want you to see

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Test::More version
Next
From: "Bossart, Nathan"
Date:
Subject: Re: Improving psql's \password command