Hi, On 6.12.2012 23:45, MauMau wrote: > From: "Tom Lane" <t...@sss.pgh.pa.us> >> Well, that's unfortunate, but it's not clear that automatic recovery is >> possible. The only way out of it would be if an undamaged copy of the >> segment was in pg_xlog/ ... but if I recall the logic correctly, we'd >> not even be trying to fetch from the archive if we had a local copy. > > No, PG will try to fetch the WAL file from pg_xlog when it cannot get it > from archive. XLogFileReadAnyTLI() does that. Also, PG manual contains > the following description: > > http://www.postgresql.org/docs/9.1/static/continuous-archiving.html#BACKUP-ARCHIVING-WAL > > > WAL segments that cannot be found in the archive will be sought in > pg_xlog/; this allows use of recent un-archived segments. However, > segments that are available from the archive will be used in preference > to files in pg_xlog/.
So why don't you use an archive command that does not create such incomplete files? I mean something like this: archive_command = 'cp %p /arch/%f.tmp && mv /arch/%f.tmp /arch/%f' Until the file is renamed, it's considered 'incomplete'. Tomas -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
