Re: A few new options for CHECKPOINT
От | Laurenz Albe |
---|---|
Тема | Re: A few new options for CHECKPOINT |
Дата | |
Msg-id | 1b097b167ecdcc903962cbe55526cdfa2c4e97cb.camel@cybertec.at обсуждение исходный текст |
Ответ на | Re: A few new options for CHECKPOINT (Bernd Helmle <mailings@oopsware.de>) |
Ответы |
Re: A few new options for CHECKPOINT
|
Список | pgsql-hackers |
On Wed, 2020-11-25 at 11:41 +0100, Bernd Helmle wrote: > Am Mittwoch, den 25.11.2020, 13:47 +0900 schrieb Michael Paquier: > > > I can see the use case for IMMEDIATE, but I fail to see the use cases > > for WAIT and FORCE. CHECKPOINT_FORCE is internally implied for the > > end-of-recovery and shutdown checkpoints. WAIT could be a dangerous > > thing if disabled, as clients could pile up requests to the > > checkpointer for no real purpose. > > Wouldn't it be more convenient to use "FAST" for immediate checkpoint, > defaulting to "FAST ON"? That would be along the parameter used in the > streaming protocol command BASE_BACKUP, where "FAST" disables lazy > checkpointing. +1 That would also match pg_basebackup's "-c fast|spread". Yours, Laurenz Albe
В списке pgsql-hackers по дате отправления: