Re: SHOW ALL does not honor pg_read_all_settings membership - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: SHOW ALL does not honor pg_read_all_settings membership
Date
Msg-id CANP8+jLwcTWfX_OnA0uPetDZmOSjS_3gVVx-TnRGG=GhrWe2ig@mail.gmail.com
Whole thread Raw
In response to Re: SHOW ALL does not honor pg_read_all_settings membership  (Michael Paquier <michael@paquier.xyz>)
Responses Re: SHOW ALL does not honor pg_read_all_settings membership
List pgsql-hackers
On 17 April 2018 at 04:28, Michael Paquier <michael@paquier.xyz> wrote:
> On Mon, Apr 16, 2018 at 02:32:10PM +0200, Laurenz Albe wrote:
>> Now that the dust from the last commitfest is settling, I'll make a second
>> attempt to attract attention for this small bug fix.
>>
>> The original commit was Simon's.
>
> Thanks for the ping.
>
> This was new as of v10, so this cannot be listed as an open item still I
> have added that under the section for older bugs, because you are right
> as far as I can see.

OK, agreed, its a bug.

Any objections to backpatch to v10?

> GetConfigOption is wrong by the way, as restrict_superuser means that
> all members of the group pg_read_all_settings can read
> GUC_SUPERUSER_ONLY params, and not only superusers, so the comment at
> least needs a fix, the variable ought to be renamed as well.

OK

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: pg_replication_slot_advance to return NULL instead of 0/0 if slotnot advanced
Next
From: Michael Paquier
Date:
Subject: Re: SHOW ALL does not honor pg_read_all_settings membership