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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Mohammad Sherafat <mhdsherafat(at)chmail(dot)ir>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: What happens if checkpoint haven't completed until the next checkpoint interval or max_wal_size?
Date: 2019-02-05 11:42:59
Message-ID: 20190205114259.GH1882@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2019-02-05 11:58:37 Internal error while setting reloption on system catalogs.
Previous Message Michael Paquier 2019-02-05 11:36:58 Re: Feature: temporary materialized views