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 1vNb8l-007zjW-1V for pgsql-admin@arkaria.postgresql.org; Mon, 24 Nov 2025 18:18:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vNb8k-002jpj-0P for pgsql-admin@arkaria.postgresql.org; Mon, 24 Nov 2025 18:18:18 +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 1vNb8j-002jpZ-1x for pgsql-admin@lists.postgresql.org; Mon, 24 Nov 2025 18:18:18 +0000 Received: from mail-oa1-x2e.google.com ([2001:4860:4864:20::2e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vNb8h-001FKw-0x for pgsql-admin@lists.postgresql.org; Mon, 24 Nov 2025 18:18:17 +0000 Received: by mail-oa1-x2e.google.com with SMTP id 586e51a60fabf-3e7e57450ceso1195080fac.2 for ; Mon, 24 Nov 2025 10:18:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1764008295; x=1764613095; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=OmJ5oCEmygY2GDOUkFzUgf2aEzbilT6GPHzXs+cGAhM=; b=Rqp4fOHzIzX/I+3ZBfMt2sw6PiuhGKte2quDcFRoy0Y7V0ICM8wo04v6qhmH5fGMrX 5wW0bQIb77VD/DHQYFEHGEvEPlVACZHc5HcsyTV4zqritjk0PhZvUbxCPo2xE2DaeZcg Ed4reOXPnVD0TOYy8vQO/TXIX595JW3YMkYzUVHN6L18Unj5mga3TtvxtWHOMbqo+faC 2hOlpVBndpKfm8W0+fm7mh1O1nttA7ukQH+sT8TVlK9dhzMzoHdYzb3WiFtFdxim/bSN yZ0JWKr6UEiAewlzVk+W+MyALODLll3Ptb7jhUPkdfgj4iPIRibyJ8cpbFuWNC0MxA8z c4Fg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764008295; x=1764613095; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=OmJ5oCEmygY2GDOUkFzUgf2aEzbilT6GPHzXs+cGAhM=; b=ST+GSQPnkrpusArDQ/53gZOFdQynvvwWIVEplOubA17stfG0nd0C2kI8ivzvTUd7P4 y535IceyPn1rENRpd8hu+NG98e98TqZ8kv/YFUR6cLv5pNjA4zTosoMCak3cSf2EZ7O/ 2P3F9MWWjSlzff9V4abW0b1f+if/T+EcTmipc7n9+uK2LOt6fn2pdbCDqrMINSb8z830 TLj1s0WPS03MH/93mYlLALULVb4bwwvG+9PZV766ao+XJmdGYroFwbfKiVAO8Ei9Qi1C 0Wr1bJLmK7g4ZeZ5yyQmj6oOQ4ol5BgsB6gdafdr83zYtD+QNWTyR6rW56GdHYObkLmS UokA== X-Gm-Message-State: AOJu0YxCNWWoqybyJeMKEynQDrAuyof3XfaVmMpOnrOgS+LKhvWNnCRX sjDaJAWx6PmprFUNJKT8m+Ow/rz9TEkanfeWm/kvmoso6om9TlxhTFqrERktDuMSMqol47fm2dc wXOl33Yg9b/cqUgBE9SgVD+iRNCk+c48= X-Gm-Gg: ASbGncsTDxDhweZUFlRNxGOV76owqFIs4wI7yL1QP0V50lYoa2YB6vgqAZ4mBrOI/li RUqyWLWfz9s+VtkuHJ0vOY+xiuR1zuxOxEWMzsHj88vanqazHdNTnfE9yI0vpr50w8UsJoq/9id d2X/rgUhcUchkAxZPGBpq7eHQiKm6+56KOSEm4/2RgqZo2/bZxPx8Hsyhs4uNdMh6QQJ4kjQsY+ lAFX50EC04TDHQy67uldm8w90URZKfH8JAHR1+JbHqYtfwYtGdFWhvi0PjEe67YRt1D4Gf9 X-Google-Smtp-Source: AGHT+IHnFEGPrWXYQaZ5RdRbOWFV9MV7X7DyqWK0BMSSzD0ueCG6SySknL4G0FGkUB6rETJiamHSzpZxwSQBxkOxL6o= X-Received: by 2002:a05:6808:309e:b0:44d:8e2c:41c0 with SMTP id 5614622812f47-45112cd5a7dmr5460419b6e.35.1764008295157; Mon, 24 Nov 2025 10:18:15 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Mon, 24 Nov 2025 12:18:04 -0600 X-Gm-Features: AWmQ_bmbP9jN_Pfffa4vQ7hYumz9JUWAiHMxv6LgTVb5nvXsPlIwzzKcgx0V7nc Message-ID: Subject: Re: Is the pg_isready database name relevant? To: Ron Johnson Cc: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000d055c806445b2f66" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d055c806445b2f66 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Nov 24, 2025, 09:53 Ron Johnson wrote: > On Mon, Nov 24, 2025 at 11:45=E2=80=AFAM David G. Johnston < > david.g.johnston@gmail.com> wrote: > >> On Monday, November 24, 2025, Ron Johnson >> wrote: >> >>> On Mon, Nov 24, 2025 at 11:30=E2=80=AFAM David G. Johnston < >>> david.g.johnston@gmail.com> wrote: >>> >>>> On Monday, November 24, 2025, Ron Johnson >>>> wrote: >>>> >>>>> The "-d, --dbname=3DDBNAME" option is mentioned in --help output, but >>>>> pg_isready ignores nonexistent databases. >>>>> >>>>> Is this an application bug, a minor doc bug or am I missing something= ? >>>>> >>>> >>>> It=E2=80=99s documented in the Notes section. >>>> >>> >>> That seems odd. Why mention an option in --help if the option isn't >>> needed? >>> >> >> Because it exists - and I figure most people should use it to not put >> spurious errors into the logs. >> > > The person on the client side isn't thinking about what's going in the PG > server's logs. > > This is something that *should* be fixed. Very low priority, after the > data corruption and feature bugs, and useful new features added, but eith= er > return an error code if the client user doesn't have access to that > database, or remove the option. > It reports whether the cluster is ready, not any specific database or for any specific user. It works just fine for its intent. Sure, it could be modified to also do something different. But you haven't explained why that would be a worthwhile use of effort. All I'm seeing it admittedly a slightly non-intuitative specification that does require reading and some degree of caring on the part of the user. And probably some recognition that it works this way because the backend protocol doesn't allow for those values to be made optional and so the current implementation is a bit of a hack to get around that fact. David J. --000000000000d055c806445b2f66 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Nov 24, 2025, 09:53 Ron Johnson <ronlj= ohnsonjr@gmail.com> wrote:
<= div dir=3D"ltr">
On Mon, Nov 24, 2025 at 11:45=E2=80=AFAM D= avid G. Johnston <david.g.johnston@gmail.com> = wrote:
On Monday, November 24, 2025, Ron Johnson <ronljohnsonjr@gmail.com> wrote:
On Mon, Nov 24, 2025 at= 11:30=E2=80=AFAM David G. Johnston <david.g.johnston= @gmail.com> wrote:
On Monday, November 24, 2025, Ron Johnson = <ronljohnsonjr@gmail.com> wrote:
The "-d, --= dbname=3DDBNAME" option is mentioned in --help output, but pg_isready = ignores=C2=A0nonexistent=C2=A0databases.

Is this a= n application bug, a minor doc bug or am I=C2=A0missing something?

It=E2=80=99s documented in the Note= s section.

That seems odd.=C2=A0 Why = mention an option in --help if the option isn't needed?

Because it exists - and I figure most pe= ople should use it to not put spurious errors into the logs.

The person on the client side isn&= #39;t thinking about what's going in the PG server's logs.

This is something that should=C2=A0be fixed.=C2=A0 = Very low priority, after the data corruption and feature bugs, and useful n= ew=C2=A0features added, but either return an error code if the client user = doesn't have access to that database, or remove the option.
=

It reports= whether the cluster is ready, not any specific database or for any specifi= c user.=C2=A0 It works just fine for its intent.=C2=A0 Sure, it could be mo= dified to also do something different.=C2=A0 But you haven't explained = why that would be a worthwhile use of effort.=C2=A0 All I'm seeing it a= dmittedly a slightly non-intuitative specification that does require readin= g and some degree of caring on the part of the user.=C2=A0 And probably som= e recognition that it works this way because the backend protocol doesn'= ;t allow for those values to be made optional and so the current implementa= tion is a bit of a hack to get around that fact.
David J.

--000000000000d055c806445b2f66--