Doug Fields <dfields-pg-general@pexicom.com> writes:
> (gdb) where
> #0 0x4028299d in fdatasync () from /lib/libc.so.6
> #1 0x081049ae in pg_fdatasync (fd=53) at fd.c:233
> #2 0x08088276 in issue_xlog_fsync () at xlog.c:3367
Hmm. That leads to a different line of thought about where the problem
is. Does the problem go away if you turn off fsync, or select a
wal_sync_method other than fdatasync? (See postgresql.conf; not sure
if you need a postmaster restart or just SIGHUP to change these.)
regards, tom lane
