Re: SHOW ALL does not honor pg_read_all_settings membership

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: pgsql-hackers(at)postgresql(dot)org, simon(at)2ndquadrant(dot)com
Subject: Re: SHOW ALL does not honor pg_read_all_settings membership
Date: 2018-04-20 13:58:06
Message-ID: 20180420135806.GA1562@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 20, 2018 at 01:21:46PM +0200, Laurenz Albe wrote:
> I agree; here is a patch for that.

Thanks for taking care of that as well this looks fine to me. Note to
committer: this needs to be merged with the first patch actually fixing
the SHOW ALL issue.

All the four core callers of GetConfigOption() actually do not use
restrict_superuser set to true... Modules may use this option, so of
course let's not remove it.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Teodor Sigaev 2018-04-20 14:18:12 Re: Corrupted btree index on HEAD because of covering indexes
Previous Message Matthias Kurz 2018-04-20 13:55:49 Add read-only param to set_config(...) / SET that effects (at least) customized runtime options