diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2010-12-08 20:01:19 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2010-12-08 20:01:19 -0500 |
commit | f3224e010dbd372a5411c5ddf0aae27f35007b65 (patch) | |
tree | d2862e387b88cefaf4b66f7cb97eaa809f0e12e2 /src/backend/access/gist/gist.c | |
parent | 234ad01f9ea08514b1368bbf214e6c779e372a1a (diff) | |
download | postgresql-f3224e010dbd372a5411c5ddf0aae27f35007b65.tar.gz postgresql-f3224e010dbd372a5411c5ddf0aae27f35007b65.zip |
Force default wal_sync_method to be fdatasync on Linux.
Recent versions of the Linux system header files cause xlogdefs.h to
believe that open_datasync should be the default sync method, whereas
formerly fdatasync was the default on Linux. open_datasync is a bad
choice, first because it doesn't actually outperform fdatasync (in fact
the reverse), and second because we try to use O_DIRECT with it, causing
failures on certain filesystems (e.g., ext4 with data=journal option).
This part of the patch is largely per a proposal from Marti Raudsepp.
More extensive changes are likely to follow in HEAD, but this is as much
change as we want to back-patch.
Also clean up confusing code and incorrect documentation surrounding the
fsync_writethrough option. Those changes shouldn't result in any actual
behavioral change, but I chose to back-patch them anyway to keep the
branches looking similar in this area.
In 9.0 and HEAD, also do some copy-editing on the WAL Reliability
documentation section.
Back-patch to all supported branches, since any of them might get used
on modern Linux versions.
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions