| From: | p(dot)luzanov(at)postgrespro(dot)ru |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pluzanov(at)postgrespro(dot)ru, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: max_wal_size |
| Date: | 2020-05-27 21:12:34 |
| Message-ID: | 8aac88e2a22cd84e50ee1a2bcf3da9b7@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
David,
> For 0.5 you get 2/3rds consumption: ( n / ( 1 + 0.5 ) ) = n * 2/3
Exactly, for checkpoint_completion_target=0.5 the distance between
checkpoints is 2/3 of max_wal_size.
But back to the documentation of max_wal_size.
"Maximum size to let the WAL grow to between automatic WAL checkpoints."
For me it looks like the distance between checkpoints is equal to
max_wal_size.
English is not my native language, so I admit that I misunderstand the
exact meaning of this phrase.
P.S. Sorry to post this topic twice.
https://www.postgresql.org/message-id/97af9ef7-d7d9-cfd0-a280-d400cf05c68a%40postgrespro.ru
-----
Pavel Luzanov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-05-27 21:54:45 | Re: max_wal_size |
| Previous Message | David G. Johnston | 2020-05-27 18:11:33 | Re: max_wal_size |