Re: Why create CHECKPOINT_WAIT checkpoint in pg_start_backup not CHECKPOINT_IMMEDIATE?

From: Greg Smith <greg(at)2ndquadrant(dot)com>
To: Richard <husttripper(at)vip(dot)sina(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Why create CHECKPOINT_WAIT checkpoint in pg_start_backup not CHECKPOINT_IMMEDIATE?
Date: 2010-08-05 19:43:58
Message-ID: 4C5B147E.50708@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Richard wrote:
> pg_start_backup is rather slow, can I change checkpoint to CHECKPOINT_IMMEDIATE?
>

Starting in PostgreSQL 8.4, pg_start_backup takes an optional second
parameter that asks it to do an immediate checkpoint if you set it
true: http://www.postgresql.org/docs/8.4/interactive/functions-admin.html

In 8.3, it can be useful to execute a manual CHECKPOINT just before
running pg_start_backup instead, so that the checkpoint it does will
likely be smaller.

--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.us

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Gordon Shannon 2010-08-05 20:00:50 Need help understanding vacuum verbose output
Previous Message Scott Marlowe 2010-08-05 19:08:29 Re: how can we resolving locking state ....