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

From Andrew Dunstan
Subject Re: Enhancement Idea - Expose the active value of a parameter in pg_settings
Date
Msg-id CAA8=A7_qXUWs3s8VEgFXho_mUYLAgeCY62X+ROYscmgQ37VzHA@mail.gmail.com
Whole thread Raw
In response to Re: Enhancement Idea - Expose the active value of a parameter in pg_settings  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Enhancement Idea - Expose the active value of a parameter in pg_settings  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Fri, May 25, 2018 at 9:58 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Greg Clough <greg.clough@ipreo.com> writes:
>> I would like to propose that we expose the "active" value of parameters in pg_settings, instead of "-1".  In this
examplebelow, when it's set to "-1" I need to know that autovacuum_work_mem is related to the setting of
maintenance_work_mem,so that I can determine that the actual setting is 64MB: 
>
> If we did that, how would you tell the difference between "-1" and a hard
> setting of 64MB?
>

He's proposing an extra column to show the actual value used, so
distinguishing them should be a problem.

cheers

andrew


--
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: In what range of the code can we read debug_query_string?
Next
From: Robert Haas
Date:
Subject: Re: Enhancement Idea - Expose the active value of a parameter in pg_settings