From: Tom Lane <tgl@sss.pgh.pa.us>
To: andy.shellam@mailnetwork.co.uk
Cc: pgsql-admin@postgresql.org
Subject: Re: WAL archive stopping too early
Date: Fri, 17 Feb 2006 09:55:37 -0500
Message-ID: <9251.1140188137@sss.pgh.pa.us> (raw)
In-Reply-To: <43F59A88.1030504@mailnetwork.co.uk>
References: <43F59A88.1030504@mailnetwork.co.uk>
Andy Shellam <andy.shellam@mailnetwork.co.uk> writes:
> Note there are plenty more files ready to run in the archive, and the
> contents of the backup label only mention 1A as the final WAL file of
> the backup, so it is starting to read the next WAL file, but stopping
> for some reason. Is it because of the "record with zero length" that's
> causing it to fail?
Yes --- that indicates the end of archive. It sounds to me like file 1B
was archived while still only partly filled. Check the process you're
using for deciding when to copy WAL files.
> Also why is it restoring 1B from the archive twice?
I think that's expected behavior --- it has something to do with wanting
to make the copy of 1B into the new writable front WAL segment. You can
dig through xlog.c if you want the details.
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 archive stopping too early
In-Reply-To: <9251.1140188137@sss.pgh.pa.us>
References: <43F59A88.1030504@mailnetwork.co.uk> <9251.1140188137@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