Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jOiTx-0008RD-Me for pgsql-bugs@arkaria.postgresql.org; Wed, 15 Apr 2020 13:53:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jOiTv-0002o4-AE for pgsql-bugs@arkaria.postgresql.org; Wed, 15 Apr 2020 13:53:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jOiTv-0002nw-41 for pgsql-bugs@lists.postgresql.org; Wed, 15 Apr 2020 13:53:35 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jOiTs-0002qN-D2 for pgsql-bugs@lists.postgresql.org; Wed, 15 Apr 2020 13:53:34 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 03FDrUkI017201; Wed, 15 Apr 2020 09:53:30 -0400 From: Tom Lane To: prd87@mail.ru cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16365: recieve smart shutdown after system start In-reply-to: <16365-6048416d452a8cbe@postgresql.org> References: <16365-6048416d452a8cbe@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Wed, 15 Apr 2020 09:40:39 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17199.1586958810.1@sss.pgh.pa.us> Date: Wed, 15 Apr 2020 09:53:30 -0400 Message-ID: <17200.1586958810@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form 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