Re: Enhancement Idea - Expose the active value of a parameter in pg_settings

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Clough <greg(dot)clough(at)ipreo(dot)com>
Cc: "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 13:58:48
Message-ID: 2883.1527256728@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-05-25 14:06:00 rule-related crash in v11
Previous Message Greg Clough 2018-05-25 13:32:37 Enhancement Idea - Expose the active value of a parameter in pg_settings