Re: fast promotion and log_checkpoints - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: fast promotion and log_checkpoints
Date
Msg-id CA+U5nMKm6-9Tvy9zw9pJ9R4uXwAaF-SqNt5Xbq1Y=vA970nn+Q@mail.gmail.com
Whole thread Raw
In response to Re: fast promotion and log_checkpoints  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On 21 May 2013 15:29, Fujii Masao <masao.fujii@gmail.com> wrote:

> Or, what about using CHECKPOINT_FORCE and just printing "force"?
> Currently that checkpoint always starts because of existence of the
> end-of-recovery record, but I think we should ensure that the checkpoint
> always starts by using that flag.

This would mean we can't use the secondary checkpoint record, but we
already gave that up so should be OK.

Three people, three suggestions; so I will agree to this suggestion so
we can get on with it.

--Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: fast promotion and log_checkpoints
Next
From: Benedikt Grundmann
Date:
Subject: Re: streaming replication, "frozen snapshot backup on it" and missing relfile (postgres 9.2.3 on xfs + LVM)