From: | "stefan" <stefan(at)intermediate(dot)de> |
---|---|
To: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | How to troubleshoot a halted postgres 8.3 ? |
Date: | 2009-10-20 12:46:43 |
Message-ID: | E28B87DDBA121F45B476C053B2171F0E596BE4@mail.intermediate.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
I have a postgres 8.3 db in which I execute a transaction with a lot of alter tabel etc, update etc statements in a single transaction.
I also execute several select statements in parallel.
This puts my database in a state which I would describe as halted, i.e. the sql interface does not respond any more, pg_admin works and shows me several transactions running.
How do I proceed to analyze what's happened? Of course, my first thought is some kind of transaction deadlock, but how do I check for this ?
In the status section of pg_admin, I can see a total of 6 transactions running, 3 in idle mode, the other 3 doing some kind of select. The lock section has several hundred lines listed, but they don't tell me what exactly is locked.
So, please give me some general idea on how to proceed with such a situation.
Thanks,
Stefan
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Mead | 2009-10-20 13:48:55 | Re: How to troubleshoot a halted postgres 8.3 ? |
Previous Message | Radamanthus Batnag | 2009-10-20 04:43:44 | WAL file compatibility |