Re: [PATCHES] Doc update for pg_start_backup

2007-06-28 Thread Tom Lane
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> Added a note to the docs that pg_start_backup can take a long time to 
> finish now that we spread out checkpoints:

Rather than suggesting twiddling checkpoint_completion_target, should
we suggest a manual CHECKPOINT command before pg_start_backup?

regards, tom lane

---(end of broadcast)---
TIP 6: explain analyze is your friend


[PATCHES] Doc update for pg_start_backup

2007-06-28 Thread Heikki Linnakangas
Added a note to the docs that pg_start_backup can take a long time to 
finish now that we spread out checkpoints:


*** doc/src/sgml/backup.sgml1 Feb 2007 00:28:16 -   2.97
--- doc/src/sgml/backup.sgml28 Jun 2007 11:44:20 -
***
*** 672,678 
  
   It does not matter which database within the cluster you connect 
to to
   issue this command.  You can ignore the result returned by the 
function;

!  but if it reports an error, deal with that before proceeding.
  
 
 
--- 672,682 
  
   It does not matter which database within the cluster you connect 
to to
   issue this command.  You can ignore the result returned by the 
function;
!  but if it reports an error, deal with that before proceeding. 
Note that
!  pg_start_backup can take a long time to finish. It performs a 
checkpoint,
!  and if one is already running it has to wait for it to finish 
first. You
!  can adjust checkpoint_completion_target to 
perform the

!  checkpoints more aggressively.
  
 
 


--
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

  http://www.postgresql.org/docs/faq