pgsql: Arrange to fsync the contents of lockfiles (both postmaster.pid - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Arrange to fsync the contents of lockfiles (both postmaster.pid
Date
Msg-id 20100816173307.3ACF67541D7@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
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.

Tags:
----
REL8_3_STABLE

Modified Files:
--------------
    pgsql/src/backend/utils/init:
        miscinit.c (r1.166.2.1 -> r1.166.2.2)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/init/miscinit.c?r1=1.166.2.1&r2=1.166.2.2)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Arrange to fsync the contents of lockfiles (both postmaster.pid
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Arrange to fsync the contents of lockfiles (both postmaster.pid