First of all: "TIP 2: Don't 'kill -9' the postmaster"
On topic: What do you mean with "locked"? Is it using 100% CPU? Or does it
give any error messages? If so, what are they?
If there is a deadlock situation, Postmaster should detect it and will then
cancel the query.
Yours,
Aarjan
----- Original Message -----
From: "Csaba Nagy" <nagy@xxxxxxxxxxxxxx>
To: "Postgres general mailing list" <pgsql-general@xxxxxxxxxxxxxx>
Sent: Friday, November 18, 2005 12:13 PM
Subject: How to debug a locked backend ?
> Hi all,
>
> I have right now a locked backend, similar to what I had a few days ago.
> It won't answer to pg_cancel_backend.
> Is there a way to diagnoze what it is actually doing ?
>
> If you answer, please do it quickly as in max 15 minutes I'll kill -9
> ...
>
> Thanks,
> Csaba.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
>
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
