pgsql: Treat a WAL sender process that hasn't started streaming yet as

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Treat a WAL sender process that hasn't started streaming yet as
Date: 2011-01-15 14:38:49
Message-ID: E1Pe7HF-0004cc-GO@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Treat a WAL sender process that hasn't started streaming yet as a regular
backend, as far as the postmaster shutdown logic is concerned. That means,
fast shutdown will wait for WAL sender processes to exit before signaling
bgwriter to finish. This avoids race conditions between a base backup stopping
or starting, and bgwriter writing the shutdown checkpoint WAL record. We don't
want e.g the end-of-backup WAL record to be written after the shutdown
checkpoint.

Branch
------
master

Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=8f5d65e916796aaee1bf7dd66daf45ca56cd13be

Modified Files
--------------
src/backend/replication/walsender.c | 10 ++++++++++
src/backend/storage/ipc/pmsignal.c | 23 +++++++++++++++++++++--
src/include/storage/pmsignal.h | 1 +
3 files changed, 32 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2011-01-15 16:55:16 pgsql: Apply patch for test_fsync to add tests for O_DIRECT.
Previous Message Simon Riggs 2011-01-14 18:09:11 Re: Re: [COMMITTERS] pgsql: Exit from base backups when shutdown is requested