On 5-Nov-08, at 1:00 PM, Tom Lane wrote:
I wrote:
Huh, is it possible that Linux rejects O_SYNC for a file on ramdisk?
I found this in the Fedora 9 manpage for open(2):
O_DIRECT support was added under Linux in kernel version
2.4.10. Older
Linux kernels simply ignore this fla
I wrote:
> Huh, is it possible that Linux rejects O_SYNC for a file on ramdisk?
I found this in the Fedora 9 manpage for open(2):
O_DIRECT support was added under Linux in kernel version 2.4.10. Older
Linux kernels simply ignore this flag. Some filesystems may not imple-
me
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 w
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
Dave Cramer <[EMAIL PROTECTED]> 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/
> 000416ED007F" (log file 5869, segme
I am trying to move a db from one machine to another.
pg_standby applies all the logs fine, then I trigger it and this
happens ???
2008-11-05 11:43:45 EST [14853] LOG: restored log file
"000316ED007E" from archive
2008-11-05 11:43:45 EST [14853] LOG: selected new timeline I
