| From: | vignesh C <vignesh21(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | describe-config issue |
| Date: | 2020-09-02 05:05:23 |
| Message-ID: | CALDaNm2+vfvRS4H4Bd=wXWtbwpP-C+XV1u-szhU+SPaR4nTk0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Postgres's describe-config option prints reset_val for int & real
configuration parameters which is not useful as it is not updated.
Printing boot_val is better in this case. reset_val is updated with
boot_val while the server is getting started but in case of postgres
--describe-config this value is not updated. I felt printing boot_val
is more appropriate in this case. Attached patch for the same.
Thoughts?
Regards,
Vignesh
EnterpriseDB: http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-describe-config-issue.patch | text/x-patch | 1.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2020-09-02 05:18:38 | A micro-optimisation for walkdir() |
| Previous Message | Justin Pryzby | 2020-09-02 04:56:44 | Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly |