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 1mIual-0001Um-Tw for pgsql-bugs@arkaria.postgresql.org; Wed, 25 Aug 2021 15:13:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mIuak-00030u-OI for pgsql-bugs@arkaria.postgresql.org; Wed, 25 Aug 2021 15:13:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mIuak-00030l-HT for pgsql-bugs@lists.postgresql.org; Wed, 25 Aug 2021 15:13:26 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mIuai-0004Lx-L3 for pgsql-bugs@lists.postgresql.org; Wed, 25 Aug 2021 15:13:25 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 17PFDMkh582100; Wed, 25 Aug 2021 11:13:22 -0400 From: Tom Lane To: Rainer Tammer cc: "David G. Johnston" , PostgreSQL mailing lists Subject: Re: Postgres 9.2.13 on AIX 7.1 In-reply-to: References: <77b4c413-b6ce-f07c-0d8b-a4ec8b5eec88@spg.schulergroup.com> <3821572.1628615273@sss.pgh.pa.us> <20217971-0a12-6a39-2b54-c13008afc3f0@spg.schulergroup.com> Comments: In-reply-to Rainer Tammer message dated "Wed, 25 Aug 2021 17:06:56 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <582098.1629904402.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Wed, 25 Aug 2021 11:13:22 -0400 Message-ID: <582099.1629904402@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Rainer Tammer writes: > 2021-08-25 16:22:33 CEST  DEBUG: postmaster received signal 2 > 2021-08-25 16:22:33 CEST  LOG:  received fast shutdown request Well, something sent the postmaster SIGINT. There isn't any mechanism within Postgres itself that would do that; you need to look for outside causes. regards, tom lane