From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lee Azzarello <lee@dropio.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Warm standby recovery failure
Date: Thu, 29 Jan 2009 20:22:01 -0500
Message-ID: <14981.1233278521@sss.pgh.pa.us> (raw)
In-Reply-To: <16b031c0901291147m17c9e176occ73994d2706f454@mail.gmail.com>
References: <16b031c0901291147m17c9e176occ73994d2706f454@mail.gmail.com>
Lee Azzarello <lee@dropio.com> writes:
> cp: writing `pg_xlog/./000000010000002F000000AA': No space left on device
> 2009-01-29 12:48:14 UTC LOG: could not read from log file 47, segment
> 170, offset 3129344: Success
> 2009-01-29 12:48:14 UTC LOG: redo done at 2F/AA2FBE08
The bottom line here seems to be that your logfile transfer process
passed a damaged (partial) WAL file to the slave postmaster, which
interpreted the damage as being end of WAL. I'm not sure whether we
could find a way to prevent it from doing that without causing bigger
problems. In any case the most useful solution is going to involve
fixing the transfer script so that it notices failures from 'cp' and
doesn't pass the broken file on to the slave.
We probably should add a caution about this to the manual's discussion
of how to write archiving scripts.
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, lee@dropio.com
Subject: Re: Warm standby recovery failure
In-Reply-To: <14981.1233278521@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