| From: | Peter Da Silva <peter(dot)dasilva(at)flightaware(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| 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:16:49 |
| Message-ID: | DA8FEB43-77DB-4072-9176-0E44A1BB93ED@flightaware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-06-08 19:21:54 | Re: pl/tcl function to detect when a request has been canceled |
| Previous Message | Alvaro Herrera | 2018-06-08 19:13:57 | Re: SHOW ALL does not honor pg_read_all_settings membership |