Skip site navigation (1) Skip section navigation (2)

Re: Unresolved error 0xC0000409 on Windows Server

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Matthew Gerber <gerber(dot)matthew(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Unresolved error 0xC0000409 on Windows Server
Date: 2012-11-05 14:15:52
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Fri, Nov 2, 2012 at 8:00 PM, Noah Misch <noah(at)leadboat(dot)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.


In response to

pgsql-hackers by date

Next:From: Amit KapilaDate: 2012-11-05 14:38:37
Subject: Re: Allow WAL information to recover corrupted pg_controldata
Previous:From: Alvaro HerreraDate: 2012-11-05 14:12:38
Subject: Re: Statistics and selectivity estimation for ranges

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group