Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qzfqf-000AMe-P9 for pgsql-admin@arkaria.postgresql.org; Sun, 05 Nov 2023 16:19:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qzfqd-009sQ3-Cg for pgsql-admin@arkaria.postgresql.org; Sun, 05 Nov 2023 16:19:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qzfqd-009sPu-1V for pgsql-admin@lists.postgresql.org; Sun, 05 Nov 2023 16:19:39 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qzfqV-004rEH-Io for pgsql-admin@lists.postgresql.org; Sun, 05 Nov 2023 16:19:38 +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 3A5GJPBs3652552; Sun, 5 Nov 2023 11:19:25 -0500 From: Tom Lane To: Rajesh Kumar cc: pgsql-admin@lists.postgresql.org, Holger Jakobs Subject: Re: Error In-reply-to: <8e083b7c-62af-289b-9665-997a38dbd65f@jakobs.com> References: <8e083b7c-62af-289b-9665-997a38dbd65f@jakobs.com> Comments: In-reply-to Holger Jakobs message dated "Sun, 05 Nov 2023 16:49:40 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3652550.1699201165.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sun, 05 Nov 2023 11:19:25 -0500 Message-ID: <3652551.1699201165@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Holger Jakobs writes: > Am 05.11.23 um 16:46 schrieb Rajesh Kumar: >> Is it because of vacuuming? > No, some application has called pg_terminate_backend() function or the = > server was shut down. > see = > https://www.postgresql.org/docs/current/functions-admin.html#FUNCTIONS-A= DMIN-SIGNAL Concretely, this indicates that something sent the server process a SIGTERM signal. At least within Postgres, that can only come from pg_terminate_backend() or the postmaster sending it because it was sent a SIGINT signal to do a fast shutdown. So, if you weren't doing this intentionally, you need to look for an external source of those signals. A common newbie mistake that could lead to this is launching the postmaster by hand, or in a shell script, in a way that doesn't dissociate it from your terminal session. In that case typing control-C or ending the session would deliver one of these signals. Make sure your postmaster start script (a) uses nohup and (b) redirects all three of postmaster's stdin, stdout, and stderr away from the terminal. Could be something else too, but in the end you've got something signaling the server that you don't want. regards, tom lane