The following bug has been logged online:
Bug reference: 4854
Logged by: Keith Pierno
Email address: kpie...@lulu.com
PostgreSQL version: 8.3.6
Operating system: Red Hat Enterprise Linux AS release 4 (Nahant Update 6)
PPC64
Description:Problems with replaying WAL
have been able to recover without them. If it helps
I can send a copy of the WAL files and my postgres.conf files.
Keith
Tom Lane wrote:
"Keith Pierno" writes:
2009-06-15 13:25:12 EDT <::> PANIC: unexpected timeline ID 6 (after 4) in
checkpoint record
database from this afternoon and this seems to be working
fine. I am just worried that another WAL file will throw the same error
and I will be without a warm standby.
Thanks again,
Keith
Tom Lane wrote:
Keith Pierno writes:
Thanks for the prompt response. If such a file is needed for
pgwalarchives]#
Keith
Tom Lane wrote:
Keith Pierno writes:
I was able to find the file, which was from the date of the failure
(Tuesday June 9th). My question is why the backup from this morning
would all of a sudden require a file from the 9th even though 5 hours
of logs were able to be
n 16 08:46 archive_status
-rw--- 1 postgres postgres 16777216 Jun 9 13:45 xlogtemp.17243
-rw--- 1 postgres postgres 16777216 Jun 9 13:45 xlogtemp.17244
-rw--- 1 postgres postgres 16777216 Jun 9 13:52 xlogtemp.17397
[postg...@db01pri ~]$
Thanks again,
Keith
Tom Lane wrote:
Ke
