Re: Unresolved error 0xC0000409 on Windows Server - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: Unresolved error 0xC0000409 on Windows Server
Date
Msg-id CAHyXU0xNNy67rBxvz7F1hOB4fiTBNOsbFDAYet52faYe2P5pAA@mail.gmail.com
Whole thread Raw
In response to Re: Unresolved error 0xC0000409 on Windows Server  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
On Fri, Nov 2, 2012 at 8:00 PM, Noah Misch <noah@leadboat.com> wrote:
>> hm, several times over the last couple of months (both on postgres 9.1
>> and 9.2), i've seen  a similar crash, but on linux.  It hits the log
>> like this:
>>
>> Execution halted  (~ 200x)
>> Error: segfault from C stack overflow
>> Execution halted  (~ 30x)
>> LOG:  server process (PID 19882) was terminated by signal 11: Segmentation fault
>> LOG:  terminating any other active server processes
>
>> note the lack of LOG in 'Execution halted', etc.  This has happened
>> several times, on different servers using different workloads (but
>> always under load).  As of yet, I've been unable to get a core but I
>> hope to get one next time it happens.  I wonder if it's a similar
>> cause?
>
> Google suggests those unadorned messages originate in R.  Do the affected
> systems use PL/R?  If so ...

yes -- they do.  I was pretty certain that no R code was running at
the time of the crash but not 100% sure.  That's a big clue -- thanks.Investigating...

merlin



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Statistics and selectivity estimation for ranges
Next
From: Amit Kapila
Date:
Subject: Re: Allow WAL information to recover corrupted pg_controldata