| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Cc: | Robert Haas <rhaas(at)postgresql(dot)org> |
| Subject: | Wrong datatype in docs for wal_summary_keep_time |
| Date: | 2024-01-08 16:37:14 |
| Message-ID: | ZZwkujFihO2uqKwp@depesz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
I was reviewing new changes, and found out that we now have
"wal_summary_keep_time" setting, but the docs
(https://www.postgresql.org/docs/devel/runtime-config-wal.html#RUNTIME-CONFIG-WAL-SUMMARIZATION)
say that it's boolean, while it is integer.
The fix is simple:
#v+
--- config.sgml 2024-01-05 10:43:17.776276803 +0100
+++ config.sgml.fixed 2024-01-08 17:35:54.202968175 +0100
@@ -4179,7 +4179,7 @@
</varlistentry>
<varlistentry id="guc-wal-summary-keep-time" xreflabel="wal_summary_keep_time">
- <term><varname>wal_summary_keep_time</varname> (<type>boolean</type>)
+ <term><varname>wal_summary_keep_time</varname> (<type>integer</type>)
<indexterm>
<primary><varname>wal_summary_keep_time</varname> configuration parameter</primary>
</indexterm>
#v-
Best regards,
depesz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2024-01-08 17:02:01 | Re: BUG #17257: (auto)vacuum hangs within lazy_scan_prune() |
| Previous Message | Alexander Korotkov | 2024-01-08 15:40:02 | Re: BUG #18261: Inconsistent results of SELECT affected by joined subqueries |