Re: got some errors after upgrade poestgresql from 9.5 to 9.6

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: 张嘉志 <zhangjiazhi(at)p1(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, backend <backend(at)p1(dot)com>, dba <dba(at)p1(dot)com>
Subject: Re: got some errors after upgrade poestgresql from 9.5 to 9.6
Date: 2016-11-23 12:51:04
Message-ID: CAB7nPqT6nSe0JDBAccsxmtxAT=C9eXGWuDdHyX-age3rZt_dvg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Nov 23, 2016 at 8:58 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> 2016-11-23 12:49 GMT+01:00 张嘉志 <zhangjiazhi(at)p1(dot)com>:
>> ===LOGS
>>
>> 2016-11-23 19:26:05.027 CST,,,7888,,58357a04.1ed0,3,,2016-11-23 19:14:12
>> CST,,0,LOG,00000,"server process (PID 7993) was terminated by signal 9:
>> Killed"
>
> It looks like somebody killed Postgres - Postgres doesn't use signal 9 what
> I know - probably someone did kill -9 on some PostgreSQL process.

This can be the OOM killer if the OS is Linux. The failure pattern
matches with what I would expect the OOM killer to do.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-11-23 15:11:34 Re: Backend receive buffer get corrupted with string: NOTICE: table "cleanup_keys" does not exist, skipping
Previous Message sarkhan.allahverdiyev 2016-11-23 12:07:25 BUG #14429: Replication configuring troubleshooting