From: Donald Fraser <postgres@kiwi-fraser.net>
To: [ADMIN] <pgsql-admin@postgresql.org>
Subject: Odd behaviour with WAL and pg_stop_backup
Date: Fri, 15 Sep 2006 13:47:21 +0100
Message-ID: <000601c6d8c5$161acd50$6464a8c0@DonAcer> (raw)
PostgreSQL 8.0.7
OS: Linux Red Hat 4.0
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.
It appears the only way to truly stop it from using the archive command is to
edit the postgresql.conf file, remove the archive command and either issue a
SIGHUP or a server restart.
Can someone confirm that this is the correct behaviour or not?
Thanks in advance,
Donald Fraser
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: postgres@kiwi-fraser.net
Subject: Re: Odd behaviour with WAL and pg_stop_backup
In-Reply-To: <000601c6d8c5$161acd50$6464a8c0@DonAcer>
References: <000601c6d8c5$161acd50$6464a8c0@DonAcer>
* 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