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 1qlUlQ-0033X6-Us for pgsql-admin@arkaria.postgresql.org; Wed, 27 Sep 2023 13:39: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 1qlUlP-004EFY-KI for pgsql-admin@arkaria.postgresql.org; Wed, 27 Sep 2023 13:39:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlUlP-004EFC-5A for pgsql-admin@lists.postgresql.org; Wed, 27 Sep 2023 13:39:39 +0000 Received: from mail-wr1-x42a.google.com ([2a00:1450:4864:20::42a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qlUlM-006vzi-I6 for pgsql-admin@lists.postgresql.org; Wed, 27 Sep 2023 13:39:37 +0000 Received: by mail-wr1-x42a.google.com with SMTP id ffacd0b85a97d-32333fb6beeso3885261f8f.0 for ; Wed, 27 Sep 2023 06:39:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20230601.gappssmtp.com; s=20230601; t=1695821975; x=1696426775; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=I+pwOMp55UNnkwn3ioqI40Utb6/rk14YthFPvBPKgcs=; b=sp8v5LRmAildiofuje3/XbQmiH09biKBszRinCmqtb6PrrJ45X5dk2rgC/RgyyKLtE MQfUY8YQgJR6AOKvqoO5dqxRZhWz1iC49JvhH4czDaDMqk14VE/n5cvpjyNzJ5kTx/pG KHXMz45NHsdUi0leNGzzWTTEy7Ari9kWcyXcXFe0+KpkS6VJUbmeuY9HB9DD89luq2Wm lgNOAJ6bYOVtPoMEpmvs2md31HZtkJOBFfiTukWlfzWiyBTJR+O6331INDXfsmSeD0c1 ZfdbWsje4bB8CqXvY/xOcJXqeMy8cA78VC7w1ByDNosmnIhXOS29t+y6OIjATX9iWZYe CCAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695821975; x=1696426775; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=I+pwOMp55UNnkwn3ioqI40Utb6/rk14YthFPvBPKgcs=; b=REsDaUn+aRbOlSyHS1rBj0j8vtW2SErJOc52qGzSyevAWe5i803VcmP7BCTaspeh78 tWN8KjAg9bfxXVTpTueU/NDQK5aOOGSzQDRFbDs6tbGQb8ADLsERfDJ2f4Y+Y6y8cVEs 3YIAwb3nNlecHWRiGOrbzP1J4LmeYk9SWop2Ca1oReHoQ1RCN9cndMa6y5wyEuBJACDx MVQocQEtbV8RJFOhNKCg4syr1BqgnFEHED6XbvuibUxDFznwvrGxSOIwNzH0szMt+D/A TnAbxntcmr78kksIatnLBirrlZzkf9wJm3A58iPPl7z3nVpnB8CH2u+dsR/OYXeHbEg1 KrzQ== X-Gm-Message-State: AOJu0YyjOxISWA4IcNtEzA0wmNx2cR0KEFvZScKq39/HpCVnxgddeovW ePuHMXBgOYFK6Z/Rn//J0IItkCTyFNW6q5XKmb0= X-Google-Smtp-Source: AGHT+IEGbuZTmNZWo7YY707Zsog6vN93+KZbjBR5AEj5vuvWQyj4jfD7vFCkU2Upb4COpAi7VMj9rg== X-Received: by 2002:a05:6000:124a:b0:319:8a28:4001 with SMTP id j10-20020a056000124a00b003198a284001mr1501646wrx.41.1695821974745; Wed, 27 Sep 2023 06:39:34 -0700 (PDT) Received: from localhost.localdomain (178-190-177-111.adsl.highway.telekom.at. [178.190.177.111]) by smtp.gmail.com with ESMTPSA id l16-20020a5d4bd0000000b003216a068d2csm17124808wrt.24.2023.09.27.06.39.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Sep 2023 06:39:34 -0700 (PDT) Message-ID: <78b8abef6c84c173aa1a5498cb3907db79d8593a.camel@cybertec.at> Subject: Re: Terminating connection because of crash of another server process From: Laurenz Albe To: Deo Felix , pgsql-admin@lists.postgresql.org Date: Wed, 27 Sep 2023 15:39:18 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 2023-09-27 at 16:25 +0300, Deo Felix wrote: > Please assist Im getting=C2=A0the error below in Postgresql 13 database >=20 > WARNING: =C2=A0terminating connection because of crash of another server = process The trick is not to have any crashes. Look at the PostgreSQL log to determine the cause of the crash and see that it does not happen again. A well configured PostgreSQL on good hardware should not crash. Yours, Laurenz Albe