Re: pg_standby could not open wal file after selecting new timeline

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_standby could not open wal file after selecting new timeline
Date: 2008-11-05 17:21:55
Message-ID: 25777.1225905715@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dave Cramer <pg(at)fastcrypt(dot)com> writes:
> 2008-11-05 11:43:45 EST [14853] LOG: selected new timeline ID: 4
> 2008-11-05 11:43:45 EST [14853] LOG: archive recovery complete
> 2008-11-05 11:43:48 EST [14853] FATAL: could not open file "pg_xlog/
> 00000004000016ED0000007F" (log file 5869, segment 127): Invalid argument

"Invalid argument"?? On the platforms I have handy, the only documented
reason for open(2) to fail with EINVAL is illegal value of the flags
argument, which should be impossible. What platform is this and what
wal_sync_method are you using?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-11-05 17:26:23 Re: broken URL in commitfest page
Previous Message Alvaro Herrera 2008-11-05 17:16:48 broken URL in commitfest page