Re: Read access for pg_monitor to pg_replication_origin_status view

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Martín Marqués <martin(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Read access for pg_monitor to pg_replication_origin_status view
Date: 2020-06-10 03:35:49
Message-ID: 20200610033549.GH38342@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-06-10 03:45:40 Re: FailedAssertion at ReorderBufferCheckMemoryLimit()
Previous Message Andrey V. Lepikhov 2020-06-10 03:05:47 Re: Global snapshots