>
> A little bit --- the timeout won't actually kill the query until the
> next time control reaches a CHECK_FOR_INTERRUPTS macro that's not inside
> a critical section. We've had issues in the past with particular code
> paths that failed to include such a check in a long-running loop, and
> there might still be some left. But by and large, it won't take very
> long for the query to notice the interrupt.
Right.I believe this is part of the standard way in which we handle
interrupts,right? Making sure that we cancel a query when the backend
is in a state to do so,not when the interrupt actually comes in,right?
Regards,
Atri
--
Regards,
Atri
l'apprenant
