Re: How to debug a locked backend ?
От | Csaba Nagy |
---|---|
Тема | Re: How to debug a locked backend ? |
Дата | |
Msg-id | 1132328192.10890.432.camel@coppola.muc.ecircle.de обсуждение исходный текст |
Ответ на | Re: How to debug a locked backend ? (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-general |
Hmm, sometimes I get my emails immediately on the list, so it's not always that bad - I had to try. I have absolutely no experience using gdb... lots of experience debugging Java, but that's a different animal. I also don't have too much time right now learning and experimenting with gdb, so I would appreciate some hints of specific manual pages to check out on how to do the connecting/stack trace. Thanks, Csaba. BTW, Tom, my mails are always bounced by your system because some reverse DNS mixup on my side. I brought this to our admins attention but it seems they won't fix it... On Fri, 2005-11-18 at 16:10, Tom Lane wrote: > Csaba Nagy <nagy@ecircle-ag.com> writes: > > 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 > > ... > > This post was pretty much a complete waste of bandwidth then, seeing > that pggeneral never has a turnaround time as short as 15 min (it seems > to be more like 2 hours today :-(). > > However, if it happens again, please see what you can learn by attaching > to the stuck backend with gdb and getting a stack trace. > > regards, tom lane
В списке pgsql-general по дате отправления: