From b01a5d9baa1ca6cca9ea3c3cda2c7869f2299b62 Mon Sep 17 00:00:00 2001 From: seanc Date: Wed, 19 Feb 2003 20:12:55 +0000 Subject: Add a patch fix a long standing bug in PostgreSQL with LISTEN/NOTIFY queues and shutting down the database. Not bumping port revision, but if you are having problems related to the above, update as necessary. Submitted by: Larry Rosenman --- .../files/patch-src::backend::commands::async.c | 38 ++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 databases/postgresql83-server/files/patch-src::backend::commands::async.c (limited to 'databases/postgresql83-server/files') diff --git a/databases/postgresql83-server/files/patch-src::backend::commands::async.c b/databases/postgresql83-server/files/patch-src::backend::commands::async.c new file mode 100644 index 000000000000..78eea1eae01c --- /dev/null +++ b/databases/postgresql83-server/files/patch-src::backend::commands::async.c @@ -0,0 +1,38 @@ +*** src/backend/commands/async.c.orig Sun Sep 15 21:24:41 2002 +--- src/backend/commands/async.c Mon Feb 17 21:38:47 2003 +*************** +*** 599,604 **** +--- 599,614 ---- + + if (notifyInterruptEnabled) + { ++ bool save_ImmediateInterruptOK = ImmediateInterruptOK; ++ ++ /* ++ * We may be called while ImmediateInterruptOK is true; turn it off ++ * while messing with the NOTIFY state. (We would have to save ++ * and restore it anyway, because PGSemaphore operations inside ++ * ProcessIncomingNotify() might reset it.) ++ */ ++ ImmediateInterruptOK = false; ++ + /* + * I'm not sure whether some flavors of Unix might allow another + * SIGUSR2 occurrence to recursively interrupt this routine. To +*************** +*** 626,631 **** +--- 636,648 ---- + elog(LOG, "Async_NotifyHandler: done"); + } + } ++ ++ /* ++ * Restore ImmediateInterruptOK, and check for interrupts if needed. ++ */ ++ ImmediateInterruptOK = save_ImmediateInterruptOK; ++ if (save_ImmediateInterruptOK) ++ CHECK_FOR_INTERRUPTS(); + } + else + { + -- cgit