Re: LWLock deadlock and gdb advice
| От | Andres Freund |
|---|---|
| Тема | Re: LWLock deadlock and gdb advice |
| Дата | |
| Msg-id | 20150729162615.GA29513@alap3.anarazel.de обсуждение |
| Ответ на | Re: LWLock deadlock and gdb advice (Jeff Janes <jeff.janes@gmail.com>) |
| Ответы |
Re: LWLock deadlock and gdb advice
|
| Список | 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 по дате отправления: