Re: Avoiding shutdown checkpoint at failover - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Avoiding shutdown checkpoint at failover
Date
Msg-id CA+U5nMLgsj78Eeh5dqZBC0kNWdcVmDJys_DF6-V7LMM0=WnknA@mail.gmail.com
Whole thread Raw
In response to Re: Avoiding shutdown checkpoint at failover  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Avoiding shutdown checkpoint at failover  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Thu, Jan 26, 2012 at 5:27 AM, Fujii Masao <masao.fujii@gmail.com> wrote:

> One thing I would like to ask is that why you think walreceiver is more
> appropriate for writing XLOG_END_OF_RECOVERY record than startup
> process. I was thinking the opposite, because if we do so, we might be
> able to skip the end-of-recovery checkpoint even in file-based log-shipping
> case.

Right now, WALReceiver has one code path/use case.

Startup has so many, its much harder to know whether we'll screw up one of them.

If we can add it in either place then I choose the simplest, most
relevant place. If the code is the same, we can move it around later.

Let me write the code and then we can think some more.

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


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: CLOG contention, part 2
Next
From: Bruce Momjian
Date:
Subject: Re: Inlining comparators as a performance optimisation