| From: | Markus Schaber <schabi(at)logix-tt(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Kill a session |
| Date: | 2006-07-14 11:28:29 |
| Message-ID: | 44B77FDD.2000900@logix-tt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi, Tom,
Tom Lane wrote:
> Our expectation is that all or at least most queries should respond to
> SIGINT or SIGTERM interrupts pretty rapidly, say on a less-than-a-second
> timescale. However there are various loops in the backend that fail to
> execute CHECK_FOR_INTERRUPTS sufficiently often :-(.
The same is true for user-defined C funtions.
The PostGIS GEOS geometry functions come to mind, for complex
geometries, they can need hours to complete. And as GEOS is a 3rd-Party
library, I don't see an easy way to make them CHECK_FOR_INTERRUPTS.
Does anybody know how this is for plpgsql, pljava and plpython?
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig A. James | 2006-07-14 15:17:38 | Re: Kill a session |
| Previous Message | Florian Weimer | 2006-07-14 07:05:31 | Re: size of pg_dump files containing bytea values |