Re: Catching query cancelations in PLPython3u - Mailing list pgsql-hackers

From Adam Brusselback
Subject Re: Catching query cancelations in PLPython3u
Date
Msg-id CAMjNa7f+j8B=Ed0gNR6i6VRdBEviwS38EyczfK1prOaOECCNEg@mail.gmail.com
Whole thread Raw
In response to Catching query cancelations in PLPython3u  (Mat Arye <mat@timescale.com>)
List pgsql-hackers
Bumping this, because I am genuinely interested if there is a better way to do this.
I'd really like to know if there is a better way than executing dummy queries...it feels dirty.


I've seen plenty of extensions not handle query cancellation / exceptions gracefully. Also seems like something to talk about in the docs a little bit, because most extensions/functions that don't handle this well aren't even aware that those issues are there from what i've seen (searching github issues, etc).

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Accept recovery conflict interrupt on blocked writing
Next
From: Tom Lane
Date:
Subject: Re: SQLFunctionCache and generic plans