My results are: Fisrt, baseline: * Linux, with fsync (default), write-cache disabled: no data corruption * Linux, with fsync (default), write-cache enabled: usually no data corruption, but two runs which had * Win32, with fsync, write-cache disabled: no data corruption * Win32, with fsync, write-cache enabled: no data corruption * Win32, with osync, write cache disabled: no data corruption * Win32, with osync, write cache enabled: no data corruption. Once I got: 2005-02-24 12:19:54 LOG: could not open file "C:/Program Files/PostgreSQL/8.0/data/pg_xlog/000000010000000000000010" (log file 0, segment 16): No such file or directory
In case anyone is wondering, you can turn off write caching on FreeBSD, for a terrible perfomance loss...
http://freebsd.active-venture.com/handbook/configtuning-disk.html#AEN8015
Chris
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
