Dave Cramer <[EMAIL PROTECTED]> 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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
