Re: [BUG] Checkpointer on hot standby runs without looking checkpoint_segments
Fujii Masao <masao.fujii@gmail.com>
From: Fujii Masao <masao.fujii@gmail.com>
To: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Cc: heikki.linnakangas@enterprisedb.com, pgsql-hackers@postgresql.org
Date: 2012-04-17T19:23:28Z
Lists: pgsql-hackers
On Tue, Apr 17, 2012 at 11:50 PM, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp> wrote: > Hmm. StandbyMode is a local variable which cannot be accessed in > checkpointer. But WalRcvInProgress() which shows if wal receiver > is running seems to be usable to ENABLE governing progress by > checkpoint_segments. Even when walreceiver is not running and WAL files are read from the archive, checkpoint_segments can trigger a restartpoint. In this case, ISTM a restartpoint should be scheduled according to checkpoint_segments, so I don't think that checking WalRcvInProgress() for that purpose is right thing. Instead, what about sharing StandbyMode flag among processes via shared memory like XLogCtl? Regards, -- Fujii Masao