Re: Kill a session
От
Markus Schaber
Тема
Re: Kill a session
Дата
Msg-id
44B77FDD.2000900@logix-tt.com
Ответ на
Re: Kill a session (Tom Lane)
Список
Дерево обсуждения
Kill a session "Craig A. James" <cjames@modgraph-usa.com>
Re: Kill a session Tino Wildenhain <tino@wildenhain.de>
Re: Kill a session "Magnus Hagander" <mha@sollentuna.net>
Re: Kill a session "Craig A. James" <cjames@modgraph-usa.com>
Re: Kill a session "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Re: Kill a session "Craig A. James" <cjames@modgraph-usa.com>
Re: Kill a session Tom Lane <tgl@sss.pgh.pa.us>
Re: Kill a session Markus Schaber <schabi@logix-tt.com>
Re: Kill a session "Craig A. James" <cjames@modgraph-usa.com>
Re: Kill a session Tom Lane <tgl@sss.pgh.pa.us>
Re: Kill a session Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Re: Kill a session Mark Kirkwood <markir@paradise.net.nz>
Re: Kill a session "Craig A. James" <cjames@modgraph-usa.com>
Re: Kill a session "Magnus Hagander" <mha@sollentuna.net>
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
В списке pgsql-performance по дате отправления
