| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | zhoushulin1992(at)gmail(dot)com |
| Subject: | The relationship between 'min_wal_size', 'max_wal_size' and 'wal_segment_size' is not record. |
| Date: | 2020-11-10 08:25:27 |
| Message-ID: | 160499672788.25505.14713165949107174380@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/bug-reporting.html
Description:
configuration option 'min_wal_size' and 'max_wal_size' must be at least
twice 'wal_segment_size', but none of these information was mentioned in the
description of these three configuration options, nor in related document in
https://www.postgresql.org/docs/11/runtime-config-wal.html,
https://www.postgresql.org/docs/11/runtime-config-preset.html, and
https://www.postgresql.org/docs/11/wal-configuration.html.
Although the default value of 'min_wal_size' and 'max_wal_size' is much
larger than 'wal_segment_size', in case of some corner case, I think it is
better to supplement this information in the doc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2020-11-10 08:28:08 | 'pg_global' cannot be used as default_tablespace. |
| Previous Message | Bruce Momjian | 2020-11-10 01:36:32 | Re: What does "[backends] should seldom or never need to wait for a write to occur" mean? |