Re: "stuck spinlock"
От | Andres Freund |
---|---|
Тема | Re: "stuck spinlock" |
Дата | |
Msg-id | 20131213002340.GD29402@awork2.anarazel.de обсуждение исходный текст |
Ответ на | Re: "stuck spinlock" (Christophe Pettus <xof@thebuild.com>) |
Ответы |
Re: "stuck spinlock"
Re: "stuck spinlock" |
Список | pgsql-hackers |
On 2013-12-12 16:22:28 -0800, Christophe Pettus wrote: > > On Dec 12, 2013, at 4:04 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > If you aren't getting a core file for a PANIC, then core > > files are disabled. > > And just like that, we get one. Stack trace: > > #0 0x00007f699a4fa425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 > (gdb) bt > #0 0x00007f699a4fa425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 > #1 0x00007f699a4fdb8b in abort () from /lib/x86_64-linux-gnu/libc.so.6 > #2 0x00007f699c81991b in errfinish () > #3 0x00007f699c81a477 in elog_finish () > #4 0x00007f699c735db3 in s_lock () > #5 0x00007f699c71e1f0 in ?? () > #6 0x00007f699c71eaf9 in ?? () Could you install the -dbg package and regenerate? Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: