From: Tom Lane <tgl@sss.pgh.pa.us>
To: andy.shellam@mailnetwork.co.uk
Cc: pgsql-admin@postgresql.org
Subject: Re: WAL recovery question - 0000001.history
Date: Fri, 28 Apr 2006 11:48:34 -0400
Message-ID: <1442.1146239314@sss.pgh.pa.us> (raw)
In-Reply-To: <20060428152301.007F011F602A@postgresql.org>
References: <20060428152301.007F011F602A@postgresql.org>
"Andy Shellam" <andy.shellam@mailnetwork.co.uk> writes:
> Basically I've taken a dump of my live database directory (between
> pg_start_backup and pg_stop_backup) calls - shipped this to my standby, set
> up a recovery.conf file (which calls the rolling-WAL script). This script
> is designed to wait until the log file arrives, or a flag file is set to
> return code 1 to postgres.
> However as soon as the recovery starts, the script is waiting for a file
> called 00000001.history, which will never arrive because it was never
> generated on the live box since the base backup was taken.
This is not a workable approach: your recovery script *will* be asked
for files that do not exist, and waiting for them to be supplied is not
always the right answer. Supplying an empty file instead is definitely
the wrong answer.
You might be able to make it work by conditionalizing the behavior on
the format of the name being asked for.
regards, tom lane
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, andy.shellam@mailnetwork.co.uk
Subject: Re: WAL recovery question - 0000001.history
In-Reply-To: <1442.1146239314@sss.pgh.pa.us>
References: <20060428152301.007F011F602A@postgresql.org> <1442.1146239314@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