"Wetzel, Juergen (Juergen)" <wetzel@avaya.com> writes:
> I'm working with postgres version 9.3.10 on Windows. From time to time a postgres process terminates with following
messages:
> LOG: server process (PID 5884) exited with exit code 3
As far as I can recall at the moment, no Postgres child process would ever
choose to exit with exit code 3; we use 0, 1, and 2, but not 3. I am
thinking that maybe you've got some custom code in plperl or plpython or
some such that does an exit(3).
> This ends up in an endless loop of these messages. Only possibility to recover is to restart postgres service.
Or maybe the exit(3) is in an extension that is preloaded into all
processes via shared_preload_libraries or similar?
regards, tom lane