| 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:51:59 |
| Message-ID: | 164.1225907519@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:
> 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)
Huh, is it possible that Linux rejects O_SYNC for a file on ramdisk?
I guess I could see an argument for doing that but it seems a tad
anal-retentive. Try setting fsync = off and see what happens.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2008-11-05 17:56:01 | Re: The suppress_redundant_updates_trigger() works incorrectly |
| Previous Message | Dave Cramer | 2008-11-05 17:37:27 | Re: pg_standby could not open wal file after selecting new timeline |