Re: REINDEX deadlock - Postgresql -9.1 - Mailing list pgsql-general

From Anoop K
Subject Re: REINDEX deadlock - Postgresql -9.1
Date
Msg-id CADK_1hKR4wxTqjB57+ec5BHhVVTTjNKg-HvbeJarcjcp7Ch6Fw@mail.gmail.com
Whole thread Raw
In response to Re: REINDEX deadlock - Postgresql -9.1  (Pavan Deolasee <pavan.deolasee@gmail.com>)
List pgsql-general
I dont have C triggers. I can attach gdb and get stacktrace. Wondering if
it will take the processes out of problem state.

Thanks
Anoop

On Thu, Feb 7, 2013 at 3:33 PM, Pavan Deolasee <pavan.deolasee@gmail.com>wrote:

> On Thu, Feb 7, 2013 at 2:08 PM, Anoop K <anoopk6@gmail.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
>

pgsql-general by date:

Previous
From: Anoop K
Date:
Subject: Re: REINDEX deadlock - Postgresql -9.1
Next
From: Alexander Farber
Date:
Subject: Re: "explain analyze" a procedure verbosely - to find which statement in it takes longer