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

pgsql: Fix NOTIFY to cope with I/O problems,such as out-of-disk-space.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix NOTIFY to cope with I/O problems,such as out-of-disk-space.
Date: 2012-06-29 04:52:14
Message-ID: E1SkTBm-0002Dw-SS@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Fix NOTIFY to cope with I/O problems, such as out-of-disk-space.

The LISTEN/NOTIFY subsystem got confused if SimpleLruZeroPage failed,
which would typically happen as a result of a write() failure while
attempting to dump a dirty pg_notify page out of memory.  Subsequently,
all attempts to send more NOTIFY messages would fail with messages like
"Could not read from file "pg_notify/nnnn" at offset nnnnn: Success".
Only restarting the server would clear this condition.  Per reports from
Kevin Grittner and Christoph Berg.

Back-patch to 9.0, where the problem was introduced during the
LISTEN/NOTIFY rewrite.

Branch
------
REL9_1_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/3ac860f6b33ffa0733d4d013718c5f408282fcb6

Modified Files
--------------
src/backend/commands/async.c |   27 ++++++++++++++++++++++-----
1 files changed, 22 insertions(+), 5 deletions(-)

pgsql-committers by date

Next:From: Peter EisentrautDate: 2012-06-29 11:04:26
Subject: pgsql: Make init-po and update-po recursive make targets
Previous:From: Alvaro HerreraDate: 2012-06-29 03:50:04
Subject: pgsql: pg_upgrade: fix off-by-one mistake in snprintf

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