pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Donald Fraser <postgres@kiwi-fraser.net>
Cc: [ADMIN] <pgsql-admin@postgresql.org>
Subject: Re: Odd behaviour with WAL and pg_stop_backup
Date: Fri, 15 Sep 2006 10:17:15 -0400
Message-ID: <24298.1158329835@sss.pgh.pa.us> (raw)
In-Reply-To: <000601c6d8c5$161acd50$6464a8c0@DonAcer>
References: <000601c6d8c5$161acd50$6464a8c0@DonAcer>

"Donald Fraser" <postgres@kiwi-fraser.net> writes:
> We have been testing the on-line backup of PostgreSQL and after issuing a 
> pg_stop_backup() PostgreSQL is still using the archive command, as set in 
> postgresql.conf, for every new WAL block generated.

Um ... why would that surprise you?  That facility is designed for
continuous archiving of WAL.  If you want to make a one-shot dump,
pg_dump is a much better tool.

			regards, tom lane



view thread (2+ messages)

Message-ID: <24298.1158329835@sss.pgh.pa.us>
Permalink:  ../24298.1158329835@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/24298.1158329835@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, postgres@kiwi-fraser.net
  Subject: Re: Odd behaviour with WAL and pg_stop_backup
  In-Reply-To: <24298.1158329835@sss.pgh.pa.us>
  References: <000601c6d8c5$161acd50$6464a8c0@DonAcer> <24298.1158329835@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox