From: | "Wetzel, Juergen (Juergen)" <wetzel(at)avaya(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Intemittendly get "server process (PID 5884) exited with exit code 3" |
Date: | 2016-04-26 12:45:21 |
Message-ID: | B21CD5EA385190469D02AC8D9D60E61A5AECD45F@AZ-FFEXMB03.global.avaya.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Tom,
many thanks for your answer. This is a good hint. Will check this.
Regards
Jürgen
-----Ursprüngliche Nachricht-----
Von: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Gesendet: Montag, 25. April 2016 17:09
An: Wetzel, Juergen (Juergen)
Cc: pgsql-general(at)postgresql(dot)org
Betreff: Re: [GENERAL] Intemittendly get "server process (PID 5884) exited with exit code 3"
"Wetzel, Juergen (Juergen)" <wetzel(at)avaya(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Rakesh Kumar | 2016-04-26 12:55:16 | Does frequent update of a row affects performance |
Previous Message | Pavel Stehule | 2016-04-26 09:21:53 | Re: Background worker with Listen |