Re: Catching query cancelations in PLPython3u

From: Adam Brusselback <adambrusselback(at)gmail(dot)com>
To: Mat Arye <mat(at)timescale(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Catching query cancelations in PLPython3u
Date: 2025-01-17 18:16:43
Message-ID: CAMjNa7f+j8B=Ed0gNR6i6VRdBEviwS38EyczfK1prOaOECCNEg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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).

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-01-17 18:27:36 Re: SQLFunctionCache and generic plans
Previous Message Andres Freund 2025-01-17 18:11:13 Re: Accept recovery conflict interrupt on blocked writing