[COMMITTERS] pgsql: Make sure that hash join's bulk-tuple-transfer loops areinterru - Mailing list pgsql-committers

From Tom Lane
Subject [COMMITTERS] pgsql: Make sure that hash join's bulk-tuple-transfer loops areinterru
Date
Msg-id E1ce7JN-0007RM-7u@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Make sure that hash join's bulk-tuple-transfer loops are interruptible.

The loops in ExecHashJoinNewBatch(), ExecHashIncreaseNumBatches(), and
ExecHashRemoveNextSkewBucket() are all capable of iterating over many
tuples without ever doing a CHECK_FOR_INTERRUPTS, so that the backend
might fail to respond to SIGINT or SIGTERM for an unreasonably long time.
Fix that.  In the case of ExecHashJoinNewBatch(), it seems useful to put
the added CHECK_FOR_INTERRUPTS into ExecHashJoinGetSavedTuple() rather
than directly in the loop, because that will also ensure that both
principal code paths through ExecHashJoinOuterGetTuple() will do a
CHECK_FOR_INTERRUPTS, which seems like a good idea to avoid surprises.

Back-patch to all supported branches.

Tom Lane and Thomas Munro

Discussion: https://postgr.es/m/6044.1487121720@sss.pgh.pa.us

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/f2ec57dee93b29e2e27235ec8cc0683d0bc7d775

Modified Files
--------------
src/backend/executor/nodeHash.c     | 6 ++++++
src/backend/executor/nodeHashjoin.c | 7 +++++++
2 files changed, 13 insertions(+)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: [COMMITTERS] pgsql: Doc: fix syntax synopsis for INSERT ... ON CONFLICT DO UPDATE.
Next
From: Tom Lane
Date:
Subject: [COMMITTERS] pgsql: Doc: fix typo in logicaldecoding.sgml.