Thread: Doc update for pg_start_backup

Doc update for pg_start_backup

From
Heikki Linnakangas
Date:
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.sgml    1 Feb 2007 00:28:16 -0000       2.97
--- doc/src/sgml/backup.sgml    28 Jun 2007 11:44:20 -0000
***************
*** 672,678 ****
       <para>
        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.
       </para>
      </listitem>
      <listitem>
--- 672,682 ----
       <para>
        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 <varname>checkpoint_completion_target</varname> to
perform the
!      checkpoints more aggressively.
       </para>
      </listitem>
      <listitem>


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

Re: Doc update for pg_start_backup

From
Tom Lane
Date:
Heikki Linnakangas <heikki@enterprisedb.com> 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