Skip site navigation (1) Skip section navigation (2)

pgsql: Arrange to fsync the contents of lockfiles (both postmaster.pid

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Arrange to fsync the contents of lockfiles (both postmaster.pid
Date: 2010-08-16 17:33:07
Message-ID: 20100816173307.3ACF67541D7@cvs.postgresql.org (view raw or flat)
Thread:
Lists: 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

Next:From: Tom LaneDate: 2010-08-16 17:33:12
Subject: pgsql: Arrange to fsync the contents of lockfiles (both postmaster.pid
Previous:From: Tom LaneDate: 2010-08-16 17:33:01
Subject: pgsql: Arrange to fsync the contents of lockfiles (both postmaster.pid

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group