Re: should we enable log_checkpoints out of the box?
От | Alvaro Herrera |
---|---|
Тема | Re: should we enable log_checkpoints out of the box? |
Дата | |
Msg-id | 202111021848.wqfnvsp6kivc@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: should we enable log_checkpoints out of the box? (Nikolay Samokhvalov <samokhvalov@gmail.com>) |
Список | pgsql-hackers |
On 2021-Nov-02, Nikolay Samokhvalov wrote: > Back to checkpoint logging. With log_checkpoints = off, and high write > activity with low max_wal_size we're already "spamming" the logs with > lots of "checkpoints are occurring too frequently" – and this happens > very often, any DBA running a restore process on Postgres with default > max_wal_size (1GB, very low for modern DBs) saw it. > > Without details, this definitely looks like "spam" Speaking of which -- I think we could easily remove checkpoint_warning without any loss of useful functionality. Or, if we have to keep it, we could change the way it works: when that condition triggers, then cause regular "checkpoint started/complete" messages to occur (if they are disabled), rather than the current "checkpoints are occurring too frequently" message. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "E pur si muove" (Galileo Galilei)
В списке pgsql-hackers по дате отправления: