From 6a294c20389911c409eb5f6f05033eaf6c6975ab Mon Sep 17 00:00:00 2001 From: cvs2svn Date: Sun, 1 Jun 2003 23:49:18 +0000 Subject: This commit was manufactured by cvs2svn to create tag 'RELEASE_5_1_0'. --- .../files/patch-src::backend::commands::async.c | 38 ---------------------- 1 file changed, 38 deletions(-) delete mode 100644 databases/postgresql84-server/files/patch-src::backend::commands::async.c (limited to 'databases/postgresql84-server/files/patch-src::backend::commands::async.c') diff --git a/databases/postgresql84-server/files/patch-src::backend::commands::async.c b/databases/postgresql84-server/files/patch-src::backend::commands::async.c deleted file mode 100644 index 78eea1eae01c..000000000000 --- a/databases/postgresql84-server/files/patch-src::backend::commands::async.c +++ /dev/null @@ -1,38 +0,0 @@ -*** 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 v1.2.3