| From: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | Anoop K <anoopk6(at)gmail(dot)com> |
| Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Venkatraju TV <venkatraju(at)gmail(dot)com> |
| Subject: | Re: REINDEX deadlock - Postgresql -9.1 |
| Date: | 2013-02-07 10:03:04 |
| Message-ID: | CABOikdPoRH78X__A2rBKZT7=9dtgwB6sreBYFw6omfvkG8Ubtw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Feb 7, 2013 at 2:08 PM, Anoop K <anoopk6(at)gmail(dot)com> wrote:
> I have the setup in problem state. But I am not able to make psql
> connections to view the lock details.
> psql connections are hanging. Is there any other info which can be collected
> in this state ?
>
Try attaching each process involved in the deadlock to gdb and print
the call stack. That may or may not be useful, but given your
situation I wonder if you have a deadlock at LWLock level. Do you have
any external module installed ? Or any triggers written in C ?
Thanks,
Pavan
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2013-02-07 10:07:41 | Re: REINDEX deadlock - Postgresql -9.1 |
| Previous Message | Chris Travers | 2013-02-07 09:38:26 | feature requests (possibly interested in working on this): functional foreign keys |