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 1vUlcB-007KgK-0B for pgsql-admin@arkaria.postgresql.org; Sun, 14 Dec 2025 12:54:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vUlcA-00Cr6O-01 for pgsql-admin@arkaria.postgresql.org; Sun, 14 Dec 2025 12:54:18 +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 ) id 1vUlc9-00Cr6F-1m for pgsql-admin@lists.postgresql.org; Sun, 14 Dec 2025 12:54:18 +0000 Received: from mail-oo1-xc2c.google.com ([2607:f8b0:4864:20::c2c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vUlc8-000gnZ-06 for pgsql-admin@lists.postgresql.org; Sun, 14 Dec 2025 12:54:18 +0000 Received: by mail-oo1-xc2c.google.com with SMTP id 006d021491bc7-6597b877066so1661773eaf.2 for ; Sun, 14 Dec 2025 04:54:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1765716853; x=1766321653; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dXw6P6224h170J7k3Z55uo6+BVxajKv13iUzuU9IDfo=; b=icz/b8Pw7mYiue2GA1oGQuOKnDb2ddv3Lc6pbdUZhHPuz2AxStogM/8Aa5W5kDVqQv CnRsPt4CJaWibmOq++7J+KuwSOy7k9E/gl7DPguUoAgwQj8dehKxbAQkJ52EtxPOjR5+ L3KqW4x/h6rm58gEK19LQ42giZPPLRU4GJF4hAlt4Zhmd5aDNqXvHwwfL3nxxECm+Qbd qGcvNVqfk4G/pFoBKuzDdqcO4wCKh9BNU5RW4BLLtNDVALHB4LYlvZqiYUZ+6y7u+lkK anSwmYj+gMMd0R5cLnYQgxD7J0tMyp5iezI9YkaEHY7idGhRFUmJ9u7IpsxLN9PtQFCb 7Diw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1765716853; x=1766321653; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=dXw6P6224h170J7k3Z55uo6+BVxajKv13iUzuU9IDfo=; b=j08J1CfKn+7Ysy1C+kIWrB+ps2v0PLPyGr6vqYSs2bp9VDUgxNAy9nc8XETm2fr3DH rQDOahGllF/pJw84N2bmL06JRNCjnB3xMnUsFeDDR4ssFnJStQ65/qN9c7NvAb2qDOou 5bLveZRoidCR5iPLptvog4Z+MpMObmowuTMU8t6PpcaWQnWrWkK9UuFSEDVVt6kDiqxk 7q/F+1PrG9A70ZE3/3sHqrmOIdSX6y/H6rENWLJcKSbQQCx61zP4tj6UNcNh/kki9za0 ltPuDhDdjXXa6U/QA2LORQFnYB8Fe8aluGtBkP4BMzOjjQ4QhFggeDWuqpVjS/BZT/3B EroA== X-Gm-Message-State: AOJu0YxH13vMp4rTuDgBTcBT+JEbMakJ6denfIQO65lEGi/ckOghAsgL TJ5gCQGf5agyPTaBJ/lmArSO5BLkkKWHD8Po9aKgWT1dxCl15msqRRe7FaHkiZf3+hJvxRgZf4Y OjrGvzRsLCniA9TxYM6nMvsoeRJSyKvNLQpTw X-Gm-Gg: AY/fxX53P1PDyxy22BM3LIiDv0t4kgmVK6TykOzDOWcW+qf9fiB7Z07dqgLKdjWtj/+ Vhu5g2+XjSKDAHsSDfdIWIABN3fWKRLCdFY6hAZPLFJF8GfeNkxFWHqWoBLH0rh3yjZtybcr3zW hnULIDwLbXqCb+93pW/Dda6qZX9DtGJM48c9uih3taVxcSr1qtoEVNXrM/mkmp2icf0iGHOZlkn 3xXgpO1t5Z5Hwylqj5gSWJRDACHgdK8peVZzdtc66LhEb4uyA0ejslCZ/Gfjx48aVlrGvUuzHFo ZFvu X-Google-Smtp-Source: AGHT+IHXmRONCrF3VnmgE4rmOvWn103ovtdztgR19Vjb9zkWGdA+00nsMo7FDB6DDjQHWRE0C9laZuJHnDmsIM48FxE= X-Received: by 2002:a4a:e911:0:b0:659:9a49:8f5a with SMTP id 006d021491bc7-65b45600753mr3606066eaf.31.1765716853263; Sun, 14 Dec 2025 04:54:13 -0800 (PST) MIME-Version: 1.0 Received: by 2002:ac9:4406:0:b0:610:c9fd:4d2f with HTTP; Sun, 14 Dec 2025 04:54:12 -0800 (PST) In-Reply-To: <6678e492-b544-4ad3-bd79-2dd3ff3cefaa@netcologne.de> References: <2046739.1758254802@sss.pgh.pa.us> <471a0d22-f769-450d-a084-74ece10915d5@netcologne.de> <6678e492-b544-4ad3-bd79-2dd3ff3cefaa@netcologne.de> From: "David G. Johnston" Date: Sun, 14 Dec 2025 05:54:12 -0700 X-Gm-Features: AQt7F2pX4NISLsJ6RQCN2y9_ucgsqlBAQRdGk1Ffu-VZf4qoOCnmfbfGtWExR6g Message-ID: Subject: Re: pgping? To: Gunnar Cc: "pgsql-admin@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000d012390645e8fdec" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d012390645e8fdec Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Saturday, December 13, 2025, Gunnar wrote: > > > On 12/13/25 15:54, David G. Johnston wrote: > > > > On Friday, December 12, 2025, Gunnar wrote: > >> >> 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, whic= h >> means nobody cares. >> >> > It isn=E2=80=99t broken - it is working precisely as intended and require= d for the > use cases it=E2=80=99s meant to solve. That=E2=80=99s why no one is fixi= ng it. These > people that want it to solve additional use cases need to step up and > implement some new features for it. > > > hm, one might argue, that if the use case 'pg_isready -d database' is > mentioned in the manual this could be seen as the aspiration, or maybe ev= en > commitment to that feature. > Even the description of pg_isready --help mentions a "connection check to > a database", not a cluster. > > Do I misinterpret the manual/help? If that was the case my next question > was ... what is the purpose of the option -d, --dbname=3DDBNAME ? > As I wrote in the other thread while rephrasing what the docs say: it avoids an inconsequential error message in the server log since the backend protocol requires any connection attempt to include those fields and sometime the defaults aren=E2=80=99t correct. David J, --000000000000d012390645e8fdec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Saturday, December 13, 2025, Gunnar <tongji@netcologne.de> wrote:
=20 =20 =20


On 12/13/25 15:54, David G. Johnston wrote:
=20

On Friday, December 12, 2025, Gunnar <tongji@netcologne.de> wrote:

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.


It isn=E2=80=99t broken - it is working precisely as intended an= d required for the use cases it=E2=80=99s meant to solve.=C2=A0 That= =E2=80=99s why no one is fixing it.=C2=A0 These people that want it to solve addition= al use cases need to step up and implement some new features for it.

hm, one might argue, that if the use case 'pg_isready -d database&#= 39; is mentioned in the manual this could be seen as the aspiration, or maybe even commitment to that feature.
Even the description of pg_isready --help mentions a "connection check to a database", not a cluster.

Do I misinterpret the manual/help? If that was the case my next question was ... what is the purpose of the option -d, --dbname=3DDBNAME ?

As I wrote in= the other thread while rephrasing what the docs say: it avoids an inconseq= uential error message in the server log since the backend protocol requires= any connection attempt to include those fields and sometime the defaults a= ren=E2=80=99t correct.

David J,
=C2=A0 --000000000000d012390645e8fdec--