Re: Enhancement Idea - Expose the active value of a parameter in pg_settings - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Enhancement Idea - Expose the active value of a parameter in pg_settings
Date
Msg-id CA+Tgmoavo_JSHS_Ti6y9gf1930uhhM5PMFp7kghZQfTPH7X5og@mail.gmail.com
Whole thread Raw
In response to Re: Enhancement Idea - Expose the active value of a parameter in pg_settings  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: Enhancement Idea - Expose the active value of a parameter in pg_settings
List pgsql-hackers
On Fri, May 25, 2018 at 10:11 AM, Andrew Dunstan
<andrew.dunstan@2ndquadrant.com> wrote:
> He's proposing an extra column to show the actual value used, so
> distinguishing them should be a problem.

For most settings, that column would just be a duplicate.  For a
handful, it would pull in the value of some other GUC.  If somebody
finds that useful, cool, they can write a view that does it and
install it on their own cluster.  I don't think that it makes a lot of
sense to put it in core, though.  My guess would be that more people
would be annoyed or confused by the extra column than would be pleased
or enlightened by it.  I could of course be wrong.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Enhancement Idea - Expose the active value of a parameter in pg_settings
Next
From: Tom Lane
Date:
Subject: Re: Enhancement Idea - Expose the active value of a parameter in pg_settings