Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_standby could not open wal file after selecting new timeline - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_standby could not open wal file after selecting new timeline
Date
Msg-id 25777.1225905715@sss.pgh.pa.us
Whole thread Raw
In response to pg_standby could not open wal file after selecting new timeline  (Dave Cramer <pg@fastcrypt.com>)
Responses Re: pg_standby could not open wal file after selecting new timeline  (Dave Cramer <pg@fastcrypt.com>)
List pgsql-hackers
Tree view 
Dave Cramer <pg@fastcrypt.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

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: broken URL in commitfest page
Next
From: Tom Lane
Date:
Subject: Re: broken URL in commitfest page