On 25 January 2013 12:15, Heikki Linnakangas <hlinnakan...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
