Re: What happens if checkpoint haven't completed until the nextcheckpoint interval or max_wal_size?

Поиск
Список
Период
Сортировка
От Kyotaro HORIGUCHI
Тема Re: What happens if checkpoint haven't completed until the nextcheckpoint interval or max_wal_size?
Дата
Msg-id 20190205.213024.209791838.horiguchi.kyotaro@lab.ntt.co.jp
обсуждение исходный текст
Ответ на Re: What happens if checkpoint haven't completed until the nextcheckpoint interval or max_wal_size?  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
At Tue, 5 Feb 2019 20:42:59 +0900, Michael Paquier <michael@paquier.xyz> wrote in <20190205114259.GH1882@paquier.xyz>
> On Tue, Feb 05, 2019 at 04:11:55PM +0530, Robert Haas wrote:
> > ...not about this part. I think the next checkpoint just doesn't start
> > until the one already in progress completes.
> 
> Yes, the requests are communicated from any backends to the
> checkpointer with shared memory (see ckpt_flags in RequestCheckpoint),
> and the backend signals the checkpointer to do the work, still it
> won't do the work until the checkpoint currently running finishes.

And, requests for checkpoints are not queued. Multiple checkpoint
requests (both automatically and manually) made during a
checkpoint are finished at once at the end of the running
checkpoint.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Kyotaro HORIGUCHI
Дата:
Сообщение: Internal error while setting reloption on system catalogs.
Следующее
От: Nikolay Shaplov
Дата:
Сообщение: Re: Ltree syntax improvement