Re: Skip checkpoint on promoting from streaming replication - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Skip checkpoint on promoting from streaming replication
Date
Msg-id CA+U5nMJzBCsutE+ZBqsDSgNf_NNq983WdxSFt3=rj6ppbUuEXA@mail.gmail.com
Whole thread Raw
In response to Re: Skip checkpoint on promoting from streaming replication  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
On 25 January 2013 12:15, Heikki Linnakangas <hlinnakangas@vmware.com> wrote:

>> 1) an immediate checkpoint can cause a disk/resource usage spike,
>> which is definitely not what you need just when a spike of connections
>> and new SQL hits the system.
>
>
> It doesn't need to be an "immediate" checkpoint, ie. you don't need to rush
> through it with checkpoint_completion_target=0. I think you should initiate
> a regular, slow, checkpoint, right after writing the end-of-recovery record.
> It can take some time for it to finish, which is ok.

OK, will add.

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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: autovacuum not prioritising for-wraparound tables
Next
From: Fujii Masao
Date:
Subject: Re: [PATCH] pg_isready (was: [WIP] pg_ping utility)