Re: LWLock deadlock and gdb advice - Mailing list pgsql-hackers

From Andres Freund
Subject Re: LWLock deadlock and gdb advice
Date
Msg-id 20150729162615.GA29513@alap3.anarazel.de
Whole thread Raw
In response to Re: LWLock deadlock and gdb advice  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: LWLock deadlock and gdb advice  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
On 2015-07-29 09:23:32 -0700, Jeff Janes wrote:
> On Tue, Jul 28, 2015 at 9:06 AM, Jeff Janes <jeff.janes@gmail.com> wrote:
> I've reproduced it again against commit b2ed8edeecd715c8a23ae462.
> 
> It took 5 hours on a 8 core "Intel(R) Xeon(R) CPU E5-2650".
> 
> I also reproduced it in 3 hours on the same machine with both JJ_torn_page
> and JJ_xid set to zero (i.e. turned off, no induced crashes), so the
> fault-injection patch should not be necessary to get the issue..

Hm, that's a single socket or dual socket E5-2650 system? That CPU
itself has 8 cores, and can work in a dual socket system, that's why I
ask.



pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: LWLock deadlock and gdb advice
Next
From: Jeff Janes
Date:
Subject: Re: LWLock deadlock and gdb advice