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

From Dave Cramer
Subject Re: pg_standby could not open wal file after selecting new timeline
Date
Msg-id 979C266A-D2E6-4AA4-8BCB-E4F64A4CC703@fastcrypt.com
Whole thread Raw
In response to Re: pg_standby could not open wal file after selecting new timeline  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_standby could not open wal file after selecting new timeline  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom,


On 5-Nov-08, at 12:21 PM, Tom Lane wrote:

> nvalid 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?

Red Hat Enterprise Linux Server release 5.2 (Tikanga)

wal_sync method is open_sync
Thing is the server is running off of a ramdisk for the move (very  
temporarily)

Dave



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: broken URL in commitfest page
Next
From: Tom Lane
Date:
Subject: Re: pg_standby could not open wal file after selecting new timeline