Tom Lane 9b178555fc Per previous discussions, get rid of use of sync(2) in favor of ... explicitly fsync'ing every (non-temp) file we have written since the last checkpoint. In the vast majority of cases, the burden of the fsyncs should fall on the bgwriter process not on backends. (To this end, we assume that an fsync issued by the bgwriter will force out blocks written to the same file by other processes using other file descriptors. Anyone have a problem with that?) This makes the world safe for WIN32, which ain't even got sync(2), and really makes the world safe for Unixen as well, because sync(2) never had the semantics we need: it offers no way to wait for the requested I/O to finish. Along the way, fix a bug I recently introduced in xlog recovery: file truncation replay failed to clear bufmgr buffers for the dropped blocks, which could result in 'PANIC: heap_delete_redo: no block' later on in xlog replay.		2004-05-31 03:48:10 +00:00
..
common	Use the new List API function names throughout the backend, and disable the	2004-05-30 23:40:41 +00:00
gist	Cleanup vectors of GISTENTRY and eliminate problem with 64-bit strict-aligned	2004-03-30 15:45:33 +00:00
hash
heap	Get rid of the former rather baroque mechanism for propagating the values	2004-05-27 17:12:57 +00:00
index	Tweak indexscan and seqscan code to arrange that steps from one page to	2004-04-21 18:24:26 +00:00
nbtree	Use the new List API function names throughout the backend, and disable the	2004-05-30 23:40:41 +00:00
rtree
transam	Per previous discussions, get rid of use of sync(2) in favor of	2004-05-31 03:48:10 +00:00
Makefile