| From: | Anoop K <anoopk6(at)gmail(dot)com> |
|---|---|
| To: | Pavan Deolasee <pavan(dot)deolasee(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:20:44 |
| Message-ID: | CADK_1hKR4wxTqjB57+ec5BHhVVTTjNKg-HvbeJarcjcp7Ch6Fw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)deolasee(at)gmail(dot)com>wrote:
> 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 | Alexander Farber | 2013-02-07 10:34:48 | Re: "explain analyze" a procedure verbosely - to find which statement in it takes longer |
| Previous Message | Anoop K | 2013-02-07 10:19:38 | Re: REINDEX deadlock - Postgresql -9.1 |