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 ) id 1vUPYf-00A37X-0A for pgsql-admin@arkaria.postgresql.org; Sat, 13 Dec 2025 13:21:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vUPYe-00Al7S-0G for pgsql-admin@arkaria.postgresql.org; Sat, 13 Dec 2025 13:21:12 +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.96) (envelope-from ) id 1vU6CM-008miA-36 for pgsql-admin@lists.postgresql.org; Fri, 12 Dec 2025 16:40:55 +0000 Received: from cc-smtpout2.netcologne.de ([89.1.8.212]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vU6CL-000LAS-19 for pgsql-admin@lists.postgresql.org; Fri, 12 Dec 2025 16:40:54 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=netcologne.de; s=nc1116a; t=1765557649; bh=fCsSNylesnoitAaleK8qTgn3acangQVi7YcXGZMy7ss=; h=Message-ID:Date:Subject:To:References:From:In-Reply-To:From; b=AOADO/TufR9OYVf1t/RqgHjuQ5p6kE7ZTihuf9meOnJQcJmN9xX02t2JxM20XNdKI Szav7LPpAhJXcpNC28R45J6SKFf27RTh43SYeClBtPZAtRI9M8aUZjm0nJIMmycAnd 4vYteBEtTnw4JZ+sYQCQr19I8RTfJFrhQHxA+UrggJlOcZc1KqAUcavbse5SmNgW1g ljYxVSp+XHFQ4h6M3Sq1HK42zD0Miv5tnWvZpE0dE8u4FJiuFNt+OssSL69geb4JL2 /gYjGfiNXzSJC3QIuPCu3eqxgJLd7FxngNeOwoMd6IlPhIHtFACy6xDi34gvFSRrvv WIkFUFDc4JEug== Received: from cc-smtpin2.netcologne.de (cc-smtpin2.netcologne.de [89.1.8.202]) by cc-smtpout2.netcologne.de (Postfix) with ESMTP id 122C311FC1 for ; Fri, 12 Dec 2025 17:40:49 +0100 (CET) Received: from [IPV6:2a03:b580:aff7:d901:d2:923d:27d5:50d1] (unknown [IPv6:2a03:b580:aff7:d901:d2:923d:27d5:50d1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by cc-smtpin2.netcologne.de (Postfix) with ESMTPSA id D202411D60 for ; Fri, 12 Dec 2025 17:40:48 +0100 (CET) Message-ID: <471a0d22-f769-450d-a084-74ece10915d5@netcologne.de> Date: Fri, 12 Dec 2025 17:41:24 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: pgping? To: pgsql-admin@lists.postgresql.org References: <2046739.1758254802@sss.pgh.pa.us> Content-Language: en-US From: Gunnar In-Reply-To: <2046739.1758254802@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-NetCologne-Spam: L List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 9/19/25 06:06, Tom Lane wrote: > Ron Johnson writes: >> On Thu, Sep 18, 2025 at 4:47 PM Ron Watkins wrote: >>> How do you install pgping on RHEL 9? >>> It doesn't appear to come with the distribution. >>> Is there some specific repo you need to use? >> What does it do that ncat and psql don't do? > pg_isready might be what the OP wants. > > regards, tom lane 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. That said I remember that I read this was broken since ... forever, which means nobody cares.