public inbox for [email protected]
help / color / mirror / Atom feedpgsql: Handle interrupts while waiting on Append's async subplans
5+ messages / 1 participants
[nested] [flat]
* pgsql: Handle interrupts while waiting on Append's async subplans
@ 2025-03-12 19:15 Heikki Linnakangas <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Heikki Linnakangas @ 2025-03-12 19:15 UTC (permalink / raw)
To: [email protected]
Handle interrupts while waiting on Append's async subplans
We did not wake up on interrupts while waiting on async events on an
async-capable append node. For example, if you tried to cancel the
query, nothing would happen until one of the async subplans becomes
readable. To fix, add WL_LATCH_SET to the WaitEventSet.
Backpatch down to v14 where async Append execution was introduced.
Discussion: https://www.postgresql.org/message-id/[email protected]
Branch
------
REL_17_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/e731e9d5eee8c9ba554b10e4f192951344dd0624
Modified Files
--------------
src/backend/executor/nodeAppend.c | 28 +++++++++++++++++++++++++---
1 file changed, 25 insertions(+), 3 deletions(-)
^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Handle interrupts while waiting on Append's async subplans
@ 2025-03-12 19:15 Heikki Linnakangas <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Heikki Linnakangas @ 2025-03-12 19:15 UTC (permalink / raw)
To: [email protected]
Handle interrupts while waiting on Append's async subplans
We did not wake up on interrupts while waiting on async events on an
async-capable append node. For example, if you tried to cancel the
query, nothing would happen until one of the async subplans becomes
readable. To fix, add WL_LATCH_SET to the WaitEventSet.
Backpatch down to v14 where async Append execution was introduced.
Discussion: https://www.postgresql.org/message-id/[email protected]
Branch
------
REL_14_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/d2fb076bec06dafd6922669eed826191c01fa9c6
Modified Files
--------------
src/backend/executor/nodeAppend.c | 28 +++++++++++++++++++++++++---
1 file changed, 25 insertions(+), 3 deletions(-)
^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Handle interrupts while waiting on Append's async subplans
@ 2025-03-12 19:15 Heikki Linnakangas <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Heikki Linnakangas @ 2025-03-12 19:15 UTC (permalink / raw)
To: [email protected]
Handle interrupts while waiting on Append's async subplans
We did not wake up on interrupts while waiting on async events on an
async-capable append node. For example, if you tried to cancel the
query, nothing would happen until one of the async subplans becomes
readable. To fix, add WL_LATCH_SET to the WaitEventSet.
Backpatch down to v14 where async Append execution was introduced.
Discussion: https://www.postgresql.org/message-id/[email protected]
Branch
------
REL_15_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/d4d34c08c75741dc2dd667fda0946ee1f6eb1544
Modified Files
--------------
src/backend/executor/nodeAppend.c | 28 +++++++++++++++++++++++++---
1 file changed, 25 insertions(+), 3 deletions(-)
^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Handle interrupts while waiting on Append's async subplans
@ 2025-03-12 19:15 Heikki Linnakangas <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Heikki Linnakangas @ 2025-03-12 19:15 UTC (permalink / raw)
To: [email protected]
Handle interrupts while waiting on Append's async subplans
We did not wake up on interrupts while waiting on async events on an
async-capable append node. For example, if you tried to cancel the
query, nothing would happen until one of the async subplans becomes
readable. To fix, add WL_LATCH_SET to the WaitEventSet.
Backpatch down to v14 where async Append execution was introduced.
Discussion: https://www.postgresql.org/message-id/[email protected]
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/af717317a04f5217728ce296edf4a581eb7e6ea0
Modified Files
--------------
src/backend/executor/nodeAppend.c | 28 +++++++++++++++++++++++++---
1 file changed, 25 insertions(+), 3 deletions(-)
^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: Handle interrupts while waiting on Append's async subplans
@ 2025-03-12 19:15 Heikki Linnakangas <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: Heikki Linnakangas @ 2025-03-12 19:15 UTC (permalink / raw)
To: [email protected]
Handle interrupts while waiting on Append's async subplans
We did not wake up on interrupts while waiting on async events on an
async-capable append node. For example, if you tried to cancel the
query, nothing would happen until one of the async subplans becomes
readable. To fix, add WL_LATCH_SET to the WaitEventSet.
Backpatch down to v14 where async Append execution was introduced.
Discussion: https://www.postgresql.org/message-id/[email protected]
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/004dbbd72f7505105a10d4e8ccb9a5a5d87125ed
Modified Files
--------------
src/backend/executor/nodeAppend.c | 28 +++++++++++++++++++++++++---
1 file changed, 25 insertions(+), 3 deletions(-)
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2025-03-12 19:15 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-03-12 19:15 pgsql: Handle interrupts while waiting on Append's async subplans Heikki Linnakangas <[email protected]>
2025-03-12 19:15 pgsql: Handle interrupts while waiting on Append's async subplans Heikki Linnakangas <[email protected]>
2025-03-12 19:15 pgsql: Handle interrupts while waiting on Append's async subplans Heikki Linnakangas <[email protected]>
2025-03-12 19:15 pgsql: Handle interrupts while waiting on Append's async subplans Heikki Linnakangas <[email protected]>
2025-03-12 19:15 pgsql: Handle interrupts while waiting on Append's async subplans Heikki Linnakangas <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox