On 10-08-01 03:03 PM, Tom Lane wrote:
The archiver will retry, *if the archive command returns non-zero exit
status*. It sounds to me like you're using an archive command script
that dutifully logs a failure but is careless about returning the proper
exit status.
That was my first thought, too
John Krasnay writes:
> We decided to do a point-in-time recovery, but that failed too, since
> the archived WAL file 000102BD0072 was zero-length. Looking
> at the logs, the archive command for this file failed at about 6:29am,
> but the server continued on until later in the evenin
Hi folks,
I recently ran into an issue with PostgreSQL 8.3 on a disk that became
full. We freed up some space and restarted PostgreSQL, but startup
failed with the following error:
2010-08-01 08:21:19 EDT FATAL: invalid data in file
"000102BD0072.0020.backup"
The indicated
