Re: describe-config issue - Mailing list pgsql-hackers

From vignesh C
Subject Re: describe-config issue
Date
Msg-id CALDaNm1ESROM-_UEd8Cw9WfhcVxPMFeX3Z16+fN7UYWjycsu4g@mail.gmail.com
Whole thread Raw
In response to Re: describe-config issue  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Sep 2, 2020 at 8:06 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Please defend that claim.  Otherwise this seems like a pretty
> random change.

I had seen that there is discrepancy in postgres --describe-config & the value displayed from pg_settings like in the below case:
postgres=# select name,min_val, max_val, boot_val,reset_val from pg_settings where name = 'checkpoint_timeout';
        name        | min_val | max_val | boot_val | reset_val
--------------------+---------+---------+----------+-----------
 checkpoint_timeout | 30      | 86400   | 300      | 300
(1 row)

[vignesh@localhost bin]$ ./postgres --describe-config | grep checkpoint_timeout
checkpoint_timeout sighup Write-Ahead Log / Checkpoints INTEGER 0 30 86400 Sets the maximum time between automatic WAL checkpoints.

In the case of pg_settings we display 300 for boot_val/reset_val whereas in the case of describe-config we display 0, shouldn't it be 300 here?
Thoughts?

 Regards,
Vignesh
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Disk-based hash aggregate's cost model
Next
From: Peter Smith
Date:
Subject: Re: proposal - function string_to_table