projects / users / kgrittn / postgres.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 7ded6d6) | patch
Arrange to fsync the contents of lockfiles (both postmaster.pid and the
authorTom Lane <[email protected]>
Mon, 16 Aug 2010 17:33:17 +0000 (17:33 +0000)
committerTom Lane <[email protected]>
Mon, 16 Aug 2010 17:33:17 +0000 (17:33 +0000)
commite521b3e9b54f118daa44c56af95894b1cefda517
treebc20506ff435610f0a17854447a66d0961900555tree
parent7ded6d69d58b40f3d7317113aeaa4df67b82e8fecommit | diff
Arrange to fsync the contents of lockfiles (both postpid and the
socket lockfile) when writing them.  The lack of an fsync here may well
explain two different reports we've seen of corrupted lockfile contents,
which doesn't particularly bother the running server but can prevent a
new server from starting if the old one crashes.  Per suggestion from
Alvaro.

Back-patch to all supported versions.
src/backend/utils/init/miscinit.c diff | blob | blame | history
Kevin Grittner's development, especially fully serializable transactions (See http://wiki.postgresql.org/wiki/Serializable for more info)