Re: Checkpointer on hot standby runs without looking checkpoint_segments
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndQuadrant.com>
To: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Cc: pgsql-hackers@postgresql.org, heikki.linnakangas@enterprisedb.com, masao.fujii@gmail.com
Date: 2012-06-29T07:10:37Z
Lists: 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