Re: Checkpointer on hot standby runs without looking checkpoint_segments - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Checkpointer on hot standby runs without looking checkpoint_segments
Date
Msg-id CA+U5nM+-u6reSJj_WS9Z2jY_otd-X4fHF1vNq35SW2j9uDjxrg@mail.gmail.com
Whole thread Raw
In response to Checkpointer on hot standby runs without looking checkpoint_segments  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: Checkpointer on hot standby runs without looking checkpoint_segments
List pgsql-hackers
On 8 June 2012 09:14, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp> wrote:

> Hello, I will make this patch start again for this CF.
>
> The requirement for this patch is as follows.
>
> - What I want to get is similarity of the behaviors between
>  master and (hot-)standby concerning checkpoint
>  progression. Specifically, checkpoints for streaming
>  replication running at the speed governed with
>  checkpoint_segments. The work of this patch is avoiding to get
>  unexpectedly large number of WAL segments stay on standby
>  side. (Plus, increasing the chance to skip recovery-end
>  checkpoint by my another patch.)

I think we need to be clearer about this:

I reject this patch and am moving to rejected on the CF manager.

The "increase chance to skip recovery end checkpoint" is completely
gone as a reason to do this (see other thread).

Plus the premise that we want more restartpoints is wrong, with
reasons explained by Heikki, in detail, months ago.

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


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Pg default's verbosity?
Next
From: Cédric Villemain
Date:
Subject: Re: We probably need autovacuum_max_wraparound_workers