From: | Nicolas <nicolas(dot)marchildon(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Mathieu Dupuis <mathd1(at)gmail(dot)com> |
Subject: | Re: Clients disconnect but query still runs |
Date: | 2009-08-06 14:23:41 |
Message-ID: | 081e9502-aca4-4747-b588-a0cfeb4f6ae3@26g2000yqk.googlegroups.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 27 juil, 21:49, t(dot)(dot)(dot)(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) wrote:
> Robert James <srobertja(dot)(dot)(dot)(at)gmail(dot)com> writes:
> > Hi. I noticed that when clients (both psql and pgAdmin) disconnect or
> > cancel, queries are often still running on the server. A few questions:
> > 1) Is there a way to reconnect and get the results?
>
> No.
>
> > 2) Is there a way to tell postgres to automatically stop all queries when
> > the client who queried them disconnects?
>
> No.
>
> > 3) Is there a way to see all queries whose clients have disconnected?
>
> No.
Ok then. Disconnection detection is hard.
Now, I'm in a situation where I have many "IDLE in transaction". I
spotted them myself. I could kill them, but that wouldn't prevent them
from happening again. In fact, it happens regularily.
Is there a way to get the list of SQL statements that were previously
executed as part of a given transaction?
If I could get that, it would be a hell lot easier to figure out the
misbehaving client.
Thanks for any pointers,
Nicolas
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2009-08-06 14:23:46 | Re: Postgresql Backups |
Previous Message | Alvaro Herrera | 2009-08-06 14:14:50 | Re: Sequence Not created with pg_dump |