Re: WAL Archiving problem

Norberto Delle <betodelle(at)gmail(dot)com> writes:
> 2007-08-20 09:12:09 LOG: archived transaction log file
> "0000000100000002000000E7"
> 2007-08-20 09:12:20 LOG: archived transaction log file
> "0000000100000002000000E8"
> 2007-08-20 09:12:21 LOG: could not receive data from client: Unknown
> winsock error 10061
> 2007-08-20 09:12:21 LOG: could not receive data from client: Unknown
> winsock error 10061
> 2007-08-20 09:12:21 LOG: unexpected EOF on client connection
> 2007-08-20 09:12:21 LOG: unexpected EOF on client connection
> 2007-08-20 09:12:21 LOG: could not receive data from client: Unknown
> winsock error 10061
> 2007-08-20 09:12:21 LOG: unexpected EOF on client connection

> -- Note that here the WAL file '0000000100000002000000E9' was archived
> (Postgres thinks it was,
> -- because it's not present in the backup directory)

> 2007-08-20 09:12:33 LOG: archived transaction log file
> "0000000100000002000000E9"
> 2007-08-20 09:12:46 LOG: archived transaction log file
> "0000000100000002000000EA"

Hmm. The broken client connections should in theory be unrelated to
anything happening with WAL files, but it does seem mighty suspicious
that they happened in the same time period that that was the active
WAL file. Do you see a lot of those "error 10061" entries elsewhere
in your logs, or was this an unusual occurrence? Also, what exactly
is your archiving script doing --- does it send the file over a network
connection? If the messages we can see above indicate a transient
network problem, as seems likely, that might possibly have affected
the archiving process as well. Are you sure your archiving script
would have noticed a network-related failure?

> -- And here Postgres is asking to archive '0000000100000002000000E9' again

> 2007-08-20 09:22:29 LOG: archive command "C:\Imob\IMOBBackup\bbp.exe
> -wal="pg_xlog\0000000100000002000000E9"" failed: return code 13

Ten minutes later --- that's a heck of a long time when you're finishing
a WAL file every ten or fifteen seconds. Please check exactly what
timestamp is on the .ready file.

regards, tom lane