| From: | "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How to release locks |
| Date: | 2006-03-22 06:56:19 |
| Message-ID: | dvqskv$1uh9$1@news.hub.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Andrus" <eetasoft(at)online(dot)ee> wrote
> After killing client from XP task manager command
>
> DELETE FROM mytable
>
> runs forever.
>
> This is probably because pgAdmin shows that there are some locks placed
(see
> included picture).
>
It is not because of the locks. There is only running transaction (and it
got every locks). Not sure why the backend stucks there, seems it doesn't
aware of the broken client. In normal situations, if you killed a client,
then the server will print something like "could not receive data from
client" then exit the backend.
If you can attach to the problematic postgres process, that would be more
helpful to identify the problem.
Regards,
Qingqing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etienne Labuschagne | 2006-03-22 07:03:52 | Re: Slow trigger on identical DB but different machine |
| Previous Message | david.hoksza | 2006-03-22 06:23:26 | Re: ambuild parameters |