Postgres Pro
Downloads
Home   >   mailing lists

Re: What happens if checkpoint haven't completed until the nextcheckpoint interval or max_wal_size? - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: What happens if checkpoint haven't completed until the nextcheckpoint interval or max_wal_size?
Date
Msg-id 20190205114259.GH1882@paquier.xyz
Whole thread Raw
In response to Re: What happens if checkpoint haven't completed until the nextcheckpoint interval or max_wal_size?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: What happens if checkpoint haven't completed until the nextcheckpoint interval or max_wal_size?  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List pgsql-hackers
Tree view 
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.
--
Michael
Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Feature: temporary materialized views
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Internal error while setting reloption on system catalogs.