Re: describe-config issue

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: describe-config issue
Date: 2020-09-03 01:52:43
Message-ID: CALDaNm1ESROM-_UEd8Cw9WfhcVxPMFeX3Z16+fN7UYWjycsu4g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 2, 2020 at 8:06 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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(at)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2020-09-03 01:52:57 Re: proposal - function string_to_table
Previous Message Peter Geoghegan 2020-09-03 00:35:13 Re: Disk-based hash aggregate's cost model