Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit e2e19ca

Browse files
committed
Seems like we should not hold off cancel/die interrupts while we are
running deferred triggers. They are really part of the regular transaction, and they could take awhile.
1 parent 602b742 commit e2e19ca

File tree

1 file changed

+4
-4
lines changed
  • src/backend/access/transam

1 file changed

+4
-4
lines changed

src/backend/access/transam/xact.c

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
*
99
*
1010
* IDENTIFICATION
11-
* $Header: /cvsroot/pgsql/src/backend/access/transam/xact.c,v 1.101 2001/03/22 06:16:10 momjian Exp $
11+
* $Header: /cvsroot/pgsql/src/backend/access/transam/xact.c,v 1.102 2001/05/04 18:39:16 tgl Exp $
1212
*
1313
* NOTES
1414
* Transaction aborts can now occur two ways:
@@ -1026,16 +1026,16 @@ CommitTransaction(void)
10261026
if (s->state != TRANS_INPROGRESS)
10271027
elog(NOTICE, "CommitTransaction and not in in-progress state ");
10281028

1029-
/* Prevent cancel/die interrupt while cleaning up */
1030-
HOLD_INTERRUPTS();
1031-
10321029
/*
10331030
* Tell the trigger manager that this transaction is about to be
10341031
* committed. He'll invoke all trigger deferred until XACT before we
10351032
* really start on committing the transaction.
10361033
*/
10371034
DeferredTriggerEndXact();
10381035

1036+
/* Prevent cancel/die interrupt while cleaning up */
1037+
HOLD_INTERRUPTS();
1038+
10391039
/*
10401040
* set the current transaction state information appropriately during
10411041
* the abort processing

0 commit comments

Comments
 (0)