From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)it>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: [SPAM] psql 9.3 automatic recovery in progress |
Date: | 2016-10-10 18:32:13 |
Message-ID: | 0d9a88d9-76f5-ac2d-8b6e-373498be0270@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/10/2016 11:14 AM, Moreno Andreo wrote:
>
> Il 10/10/2016 18:24, Periko Support ha scritto:
>> 2016-09-12 09:00:01 PDT LOG: server process (PID 23958) was
>> terminated by signal 9: Killed
>
>> 2016-09-12 10:00:01 PDT LOG: server process (PID 30766) was
>> terminated by signal 9: Killed
>
>> 2016-09-12 15:00:01 PDT LOG: server process (PID 22030) was
>> terminated by signal 9: Killed
>>
>>
> These datetimes could be suspect. Every crash (kill) is done at
> "00"minutes and "01" minutes, that makes me ask "Isn't there something
> like cron running something that interfere with postgres?"
While we on the subject, the datetimes are almost a month old.
Does that mean this problem was just noticed or are the datetimes wrong?
>
> Cheers,
> Moreno.
>
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Periko Support | 2016-10-10 19:12:33 | Re: psql 9.3 automatic recovery in progress |
Previous Message | Tom Lane | 2016-10-10 18:22:14 | Re: psql 9.3 automatic recovery in progress |