Re: Postgres 9.2.8 crash sporadically on Windows - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Postgres 9.2.8 crash sporadically on Windows
Date
Msg-id 18921.1396883732@sss.pgh.pa.us
Whole thread Raw
In response to Re: Postgres 9.2.8 crash sporadically on Windows  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Postgres 9.2.8 crash sporadically on Windows
List pgsql-bugs
Andres Freund <andres@2ndquadrant.com> writes:
> On 2014-04-07 09:49:09 -0500, Sofer, Yuval wrote:
>> Postgres server (9.2.8) crash on Windows sporadically

>> 2014-04-06 08:08:01.069 GMTLOG:  server process (PID 5304) exited with exit code 0
>> 2014-04-06 08:08:01.069 GMTLOG:  terminating any other active server processes
>> 2014-04-06 08:08:01.833 GMTLOG:  all server processes terminated; reinitializing
>> 2014-04-06 08:08:11.183 GMTFATAL:  pre-existing shared memory block is still in use
>> 2014-04-06 08:08:11.183 GMTHINT:  Check if there are any old server processes still running, and terminate them.
>>
>> This is production, Please help!

> This is unfortunately not giving us many details to work with...

The "exit code 0" bit reminds me of this:

http://www.postgresql.org/message-id/21027.1393546453@sss.pgh.pa.us

Is there another exit report for the same PID just above the quoted log
extract?  Because if there isn't, the postmaster shouldn't be thinking
that status 0 represents a crash.

            regards, tom lane

pgsql-bugs by date:

Previous
From: sqlpro@sqlspot.com
Date:
Subject: BUG #9896: Bug in FULL OUTER JOIN
Next
From: Andres Freund
Date:
Subject: Re: Postgres 9.2.8 crash sporadically on Windows