| 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:05:12 |
| Message-ID: | C82A8B79-027A-4A6D-89FE-5859C240A409@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 :/
That seems to work, and I suppose in most cases the overhead could be mitigated by only calling it every N times through a loop, but it's not as clean.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-06-08 19:08:12 | Re: Performance regression with PostgreSQL 11 and partitioning |
| Previous Message | Robert Haas | 2018-06-08 18:52:40 | Re: Performance regression with PostgreSQL 11 and partitioning |