From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, masao(dot)fujii(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Skip checkpoint on promoting from streaming replication |
Date: | 2013-01-25 13:26:30 |
Message-ID: | CA+U5nMJzBCsutE+ZBqsDSgNf_NNq983WdxSFt3=rj6ppbUuEXA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 25 January 2013 12:15, Heikki Linnakangas <hlinnakangas(at)vmware(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-01-25 13:26:51 | Re: [BUGS] BUG #7515: DROP TABLE IF EXISTS fails if schema does not exist |
Previous Message | Andres Freund | 2013-01-25 13:22:40 | Re: [BUGS] BUG #7515: DROP TABLE IF EXISTS fails if schema does not exist |