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 1v9WCg-001pAS-2A for pgsql-docs@arkaria.postgresql.org; Thu, 16 Oct 2025 22:12:09 +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 1v9WCe-00Fuiw-Uz for pgsql-docs@arkaria.postgresql.org; Thu, 16 Oct 2025 22:12:07 +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 1v9WCe-00Fuin-Na for pgsql-docs@lists.postgresql.org; Thu, 16 Oct 2025 22:12:07 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1v9WCb-002Af9-0a for pgsql-docs@lists.postgresql.org; Thu, 16 Oct 2025 22:12:06 +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 59GMC3wD1569202; Thu, 16 Oct 2025 18:12:03 -0400 From: Tom Lane To: kes-kes@yandex.ru cc: pgsql-docs@lists.postgresql.org Subject: Re: Can not close psql In-reply-to: <176062103146.770.13933926146695087061@wrigleys.postgresql.org> References: <176062103146.770.13933926146695087061@wrigleys.postgresql.org> Comments: In-reply-to PG Doc comments form message dated "Thu, 16 Oct 2025 13:23:51 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1569200.1760652723.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 16 Oct 2025 18:12:03 -0400 Message-ID: <1569201.1760652723@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Doc comments form writes: > I was connected to database via `psql` then I rebooted DB. I was not abl= e to > disconnect from terminal after that. Only whole window close helped. A documentation comment is a very poor way to submit a trouble report... > FATAL: terminating connection due to administrator command > SSL connection has been closed unexpectedly > The connection to the server was lost. Attempting reset: > ^C^C^C^C Hmm. When I try this I get either postgres=3D# \d FATAL: terminating connection due to administrator command SSL connection has been closed unexpectedly The connection to the server was lost. Attempting reset: Failed. !?> = or postgres=3D# \d FATAL: terminating connection due to administrator command SSL connection has been closed unexpectedly The connection to the server was lost. Attempting reset: Succeeded. SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compres= sion: off, ALPN: postgresql) postgres=3D# = (depending on whether I restarted the server yet), with pretty much no delay. You'll need to provide a lot more context about your setup if you want useful help. What's the platform? Is the server on the same machine as psql, or remote? What connection options are you using besides SSL? What OpenSSL version is psql using? For that matter, which psql version is it? https://wiki.postgresql.org/wiki/Guide_to_reporting_problems regards, tom lane