| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Peter Da Silva <peter(dot)dasilva(at)flightaware(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pl/tcl function to detect when a request has been canceled |
| Date: | 2018-06-08 19:21:54 |
| Message-ID: | 20180608192154.shvmozcpstpnhlyf@alap3.anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-06-08 19:16:49 +0000, Peter Da Silva wrote:
> On 6/8/18, 1:12 PM, "Andres Freund" <andres(at)anarazel(dot)de> wrote:
> I'm not terribly opposed to this, but I wonder if the much more
> pragmatic solution is to just occasionally call a database function that
> checks this? You could just run SELECT 1 occasionally :/
>
> After further discussion with our team:
>
> Would this work if the reason for it ignoring the cancel request is
> that it is already performing a long-running spi_exec with a large
> response?
Not sure I quite understand what you mean. You're thinking of the case
where you're processing rows one-by-one with a cursor? Or that a single
spi call takes a long while to process the query?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-06-08 19:23:18 | Re: pl/tcl function to detect when a request has been canceled |
| Previous Message | Peter Da Silva | 2018-06-08 19:16:49 | Re: pl/tcl function to detect when a request has been canceled |