Re: LWLock deadlock and gdb advice

On Tue, Jun 30, 2015 at 6:25 AM, Peter Geoghegan <pg@heroku.com> wrote:
>
> On Mon, Jun 29, 2015 at 5:37 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
> > Is there a way to use gdb to figure out who holds the lock they are waiting
> > for?
>
> Have you considered building with LWLOCK_STATS defined, and LOCK_DEBUG
> defined? That might do it.
>

If you define LOCK_DEBUG, then you can check owner of the

lock [1], which will tell you about the Exclusive owner of that lock

and can help you in debugging the problem.

[1]