| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Greg Clough <greg(dot)clough(at)ipreo(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Enhancement Idea - Expose the active value of a parameter in pg_settings |
| Date: | 2018-05-25 14:11:49 |
| Message-ID: | CAA8=A7_qXUWs3s8VEgFXho_mUYLAgeCY62X+ROYscmgQ37VzHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 25, 2018 at 9:58 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Greg Clough <greg(dot)clough(at)ipreo(dot)com> writes:
>> I would like to propose that we expose the "active" value of parameters in pg_settings, instead of "-1". In this example below, 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-05-25 14:16:49 | Re: Enhancement Idea - Expose the active value of a parameter in pg_settings |
| Previous Message | Tom Lane | 2018-05-25 14:08:08 | Re: In what range of the code can we read debug_query_string? |