@vonzshik

...but since we want to backport this to 7.0, 6.0 and 5.0...

Is the same issue present in any of 6.0 releases or "backport" means something else?

Is the same issue present in any of 6.0 releases or "backport" means something else?

Yeah, it was introduced with #4907, which was backported to 7.0.2, 6.0.9 and 5.0.16.

we won't cancel a running query if a cancellation token is triggered before we were able to read all of the responses for the prepended queries

Is there going to be a different fix in 8.0 where the cancellation is guaranteed to happen (async continuation, or some other way)?

Is there going to be a different fix in 8.0 where the cancellation is guaranteed to happen (async continuation, or some other way)?

That's the plan, for now I'm waiting for @roji to take a look so we can discuss further.

This is high on my list, I'm finishing up some large/intensive unrelated work and will look at this soon.

Backported to 7.0.4 via 72bef2b, 6.0.10 via 106a012, 5.0.16 via 3881c6c.