aboutsummaryrefslogtreecommitdiff
path: root/src/interfaces/ecpg/test
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-08-16 17:33:01 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-08-16 17:33:01 +0000
commite74ced85dc9b6520450d6dbf8ba9cf272c1465db (patch)
treed3bb3165b41d3af75753b7c9cc25ffb691798d83 /src/interfaces/ecpg/test
parent00fb7f5e58738e02a3649a8f0c8e20dadb8f1af7 (diff)
downloadpostgresql-e74ced85dc9b6520450d6dbf8ba9cf272c1465db.tar.gz
postgresql-e74ced85dc9b6520450d6dbf8ba9cf272c1465db.zip
Arrange to fsync the contents of lockfiles (both postmaster.pid 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.
Diffstat (limited to 'src/interfaces/ecpg/test')
0 files changed, 0 insertions, 0 deletions