Re: "Hanging Connection" blocks access to table (JBossMQ)
От | Markus Schaber |
---|---|
Тема | Re: "Hanging Connection" blocks access to table (JBossMQ) |
Дата | |
Msg-id | 452F7E19.5020800@logix-tt.com обсуждение исходный текст |
Ответ на | Re: "Hanging Connection" blocks access to table (JBossMQ) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: "Hanging Connection" blocks access to table (JBossMQ)
|
Список | pgsql-jdbc |
Hi, Tom, Tom Lane wrote: > Michael Goldner <mgoldner@agmednet.com> writes: >> When I shutdown Jboss, the idle process disappears, but the 2 "INSERT >> waiting" processes remain indefinitely. > > Ah. That makes sense, because a backend blocked partway through a query > isn't going to notice its client disconnecting. The question here > though is still "what are they waiting for?". See pg_locks. Is there any possibility that we make a backend realize this SIGIO (or whatever it gets) when the connection is closed? I often had the problem that I shut down my application, but the server kept working on that query for a long time. The same is for very long running C-Code functions (like PostGIS geomUnion() on geometries with millions of vertices), those also tend to block the backend for long times, without any possibility to kill it except SIGKILL. Thanks, Markus -- Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in Europe! www.ffii.org www.nosoftwarepatents.org
В списке pgsql-jdbc по дате отправления: