From: Пивницкий Роман <prd87@mail.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re[2]: BUG #16365: recieve smart shutdown after system start
Date: Wed, 15 Apr 2020 18:05:36 +0300
Message-ID: <1586963136.565209093@f514.i.mail.ru> (raw)
In-Reply-To: <17200.1586958810@sss.pgh.pa.us>
References: <16365-6048416d452a8cbe@postgresql.org>
<17200.1586958810@sss.pgh.pa.us>
Thanks for the answer.
The only thing that united all the servers on which this behavior manifested was a shutdown on command from the UPS.
The UPS software has now changed. There was apcupsd, became chick-monitoring.
However, the behavior of postgresql persisted.
Completion does not apply to any other system processes. But it applies to all elements of the cluster (i.e., it was originally 1 - main, now there are 2 of them).
>Среда, 15 апреля 2020, 17:53 +04:00 от Tom Lane <tgl@sss.pgh.pa.us>:
>
>PG Bug reporting form < noreply@postgresql.org > writes:
>> On some servers, we began to encounter the "strange" behavior of
>> postgresql.
>> When shutting down the server at the command of UPS (shutdown now). The next
>> time you turn on postgresql, it gets smart shutdown immediately at startup
>Something is sending the server a SIGTERM signal. This is not a
>Postgres bug, it's something else in your system doing something
>it shouldn't.
>
>regards, tom lane
С уважением.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: prd87@mail.ru, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: Re[2]: BUG #16365: recieve smart shutdown after system start
In-Reply-To: <1586963136.565209093@f514.i.mail.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox