Re: "stuck spinlock"

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "stuck spinlock"
Date: 2013-12-13 00:22:28
Message-ID: 1B343C07-4CA5-4F8B-92FC-7ACC68B05250@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Dec 12, 2013, at 4:04 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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 ?? ()
#7 0x00007f699c71f53e in ReadBufferExtended ()
#8 0x00007f699c56d03a in index_fetch_heap ()
#9 0x00007f699c67a0b7 in ?? ()
#10 0x00007f699c66e98e in ExecScan ()
#11 0x00007f699c6679a8 in ExecProcNode ()
#12 0x00007f699c67407f in ExecAgg ()
#13 0x00007f699c6678b8 in ExecProcNode ()
#14 0x00007f699c664dd2 in standard_ExecutorRun ()
#15 0x00007f6996ad928d in ?? ()
from /usr/lib/postgresql/9.3/lib/auto_explain.so
#16 0x00007f69968d3525 in ?? ()
from /usr/lib/postgresql/9.3/lib/pg_stat_statements.so
#17 0x00007f699c745207 in ?? ()
#18 0x00007f699c746651 in PortalRun ()
#19 0x00007f699c742960 in PostgresMain ()
#20 0x00007f699c6ff765 in PostmasterMain ()
#21 0x00007f699c53bea2 in main ()

--
-- Christophe Pettus
xof(at)thebuild(dot)com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-12-13 00:23:41 Re: "stuck spinlock"
Previous Message Peter Geoghegan 2013-12-13 00:18:33 Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE