Re: Is Pg 7.0.x's Locking Mechanism BROKEN? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Is Pg 7.0.x's Locking Mechanism BROKEN?
Date
Msg-id 9089.964729394@sss.pgh.pa.us
Whole thread Raw
In response to Re: Is Pg 7.0.x's Locking Mechanism BROKEN?  (frank <f.callaghan@ieee.org>)
List pgsql-hackers
Frank and Fabrice,

If you aren't having any luck generating a reproducible example of this
problem, you might try recompiling the backend with LOCK_DEBUG defined
in src/include/config.h --- or just dogmake cleangmake PROFILE=-DLOCK_DEBUG all
This should produce pretty voluminous quantities of info in the
postmaster's stdout/stderr log.  Run the postmaster with -d2 so we
can see the related queries too, and then maybe the log will have enough
info to tell something useful the next time you see it happen.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Questionable coding in proc.c & lock.c
Next
From: Joe Brenner
Date:
Subject: Re: Inprise InterBase(R) 6.0 Now Free and Open Source