| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | pluzanov(at)postgrespro(dot)ru, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: max_wal_size |
| Date: | 2020-05-27 15:40:29 |
| Message-ID: | CAKFQuwZOwfUwOxNh5KjUjCSFaecUWxtHEbPHEK8CJF1+zn9Bjg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wed, May 27, 2020 at 8:18 AM PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/runtime-config-wal.html
> Description:
>
> About parameter max_wal_size the documentation says that "Maximum size to
> let the WAL grow to between automatic WAL checkpoints."
> Is it correct?
> The size between automatic WAL checkpoints or the size of the whole pg_wal
> directory?
>
Reading on... "This is a soft limit; WAL size can exceed max_wal_size under
special circumstances"
The database doesn't provide an option that would basically mean "make sure
the wal directory doesn't get larger than X even if that means that it will
become corrupted should it crash".
This setting is the indirect means to ensure that the WAL directory doesn't
get too large by forcing a checkpoint thus allowing the corresponding WAL
to be removed.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | p.luzanov | 2020-05-27 16:17:23 | Re: max_wal_size |
| Previous Message | Egor Rogov | 2020-05-27 10:28:14 | Re: max_wal_size |