On 2014-04-07 11:15:32 -0400, Tom Lane wrote:
> 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.
Wouldn't a pl or library doing a exit(0); cause exactly that, because it
will still be in PM_CHILD_ASSIGNED?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
