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.96)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1vUS20-00BW2d-0N
	for pgsql-admin@arkaria.postgresql.org;
	Sat, 13 Dec 2025 15:59:40 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.96)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1vUS1z-00B3T4-0H
	for pgsql-admin@arkaria.postgresql.org;
	Sat, 13 Dec 2025 15:59: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.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1vUS1y-00B3Sw-2Q
	for pgsql-admin@lists.postgresql.org;
	Sat, 13 Dec 2025 15:59: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.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1vUS1x-000YHX-0e
	for pgsql-admin@lists.postgresql.org;
	Sat, 13 Dec 2025 15:59:39 +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 5BDFxZMW1179786;
	Sat, 13 Dec 2025 10:59:35 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gunnar <tongji@netcologne.de>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: pgping?
In-reply-to: <471a0d22-f769-450d-a084-74ece10915d5@netcologne.de>
References: 
 <CAPdrarpx11sa=W2dQhLAhQGQ=2a_wtMmB8KPqEY-C4ZbJem1JA@mail.gmail.com>
 <CANzqJaApzEfVtBqvitzFunaVNpwTDy=rNorXm0_YAuCFVO_c=w@mail.gmail.com>
 <2046739.1758254802@sss.pgh.pa.us>
 <471a0d22-f769-450d-a084-74ece10915d5@netcologne.de>
Comments: In-reply-to Gunnar <tongji@netcologne.de>
	message dated "Fri, 12 Dec 2025 17:41:24 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1179784.1765641575.1@sss.pgh.pa.us>
Date: Sat, 13 Dec 2025 10:59:35 -0500
Message-ID: <1179785.1765641575@sss.pgh.pa.us>
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Archived-At: 
 <https://www.postgresql.org/message-id/1179785.1765641575%40sss.pgh.pa.us>
Precedence: bulk

Gunnar <tongji@netcologne.de> writes:
> On 9/19/25 06:06, Tom Lane wrote:
>> pg_isready might be what the OP wants.

> my latest experience with pg_isready reminded me that it only works on a 
> general level (cluster ready generally) though.
> If you include a database to the command it still reports true even if 
> the database you want to address does not exist.

If you want to see whether you can log in, then try to log in, using
psql or pretty much any other client.  That is not the problem that
pg_isready seeks to solve.

			regards, tom lane