Re: assessing parallel-safety

From: Thom Brown <thom(at)linux(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: assessing parallel-safety
Date: 2015-03-20 15:08:15
Message-ID: CAA-aLv5K1N_Q-jDdtTw8T8uYuOETFF0HubMMXMFFUqJ7zEpXvA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 20 March 2015 at 15:02, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Mar 20, 2015 at 10:24 AM, Thom Brown <thom(at)linux(dot)com> wrote:
>> 2015-03-20 14:19:31 GMT [4273]: [78-1] user=,db=,client= DEBUG:
>> server process (PID 4285) was terminated by signal 11: Segmentation
>> fault
>
> Any chance you can get us a stack backtrace of this crash?

(gdb) cont
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x0000000000770843 in pfree ()
(gdb) bt
#0 0x0000000000770843 in pfree ()
#1 0x00000000005a382f in ExecEndFunnel ()
#2 0x000000000059fe75 in ExecEndAppend ()
#3 0x00000000005920bd in standard_ExecutorEnd ()
#4 0x000000000055004b in ExplainOnePlan ()
#5 0x000000000055025d in ExplainOneQuery ()
#6 0x000000000055064d in ExplainQuery ()
#7 0x0000000000680db1 in standard_ProcessUtility ()
#8 0x000000000067e1c1 in PortalRunUtility ()
#9 0x000000000067ef1d in FillPortalStore ()
#10 0x000000000067f8eb in PortalRun ()
#11 0x000000000067d628 in PostgresMain ()
#12 0x0000000000462c5e in ServerLoop ()
#13 0x000000000062e363 in PostmasterMain ()
#14 0x00000000004636ad in main ()

--
Thom

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-03-20 15:25:27 Re: assessing parallel-safety
Previous Message Robert Haas 2015-03-20 15:02:56 Re: assessing parallel-safety