Re: WAL recovery question - 0000001.history

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: andy(dot)shellam(at)mailnetwork(dot)co(dot)uk
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: WAL recovery question - 0000001.history
Date: 2006-04-28 15:48:34
Message-ID: 1442.1146239314@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Andy Shellam" <andy(dot)shellam(at)mailnetwork(dot)co(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Benjamin Krajmalnik 2006-04-28 15:53:14 Re: New system recommendations
Previous Message Andy Shellam 2006-04-28 15:34:35 Re: Backing up large databases