andy rost <[EMAIL PROTECTED]> writes:
> I'm curious about a couple of things. Why didn't the logs reflect the
> problem that it noticed when it tried to restart on 2006-12-04(what I
> mean by that, is Postgres thought the server had been interrupted on
> 2006-12-02 16:45 yet the logs for that da
We perform a daily PTR backups of the database. Part of this process is
to delete old archived WALs between backups (no need to keep archived
transaction logs that are older than the most recent full backup, or is
there?). Since we had no indication of a problem, and since the server
continued
andy rost <[EMAIL PROTECTED]> writes:
> We stopped postgres using kill -TERM. When we tried to restart the
> engine, it would not recover.
Since you're apparently using archiving, you could pull the missing xlog
files back from the archive no? Either manually, or automatically by
installing a re
Running Postgres version 8.1.3 on Opteron box running FreeBSD
6.0-RELEASE #10.
We stopped postgres using kill -TERM. When we tried to restart the
engine, it would not recover. The logs stated the following:
2006-12-04 10:18:39 CST LOG: archived transaction log file
"0001006900
