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

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:37:27
Message-ID: 979C266A-D2E6-4AA4-8BCB-E4F64A4CC703@fastcrypt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-11-05 17:51:59 Re: pg_standby could not open wal file after selecting new timeline
Previous Message Simon Riggs 2008-11-05 17:35:51 Re: broken URL in commitfest page