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 1vNbM4-0086a2-36 for pgsql-admin@arkaria.postgresql.org; Mon, 24 Nov 2025 18:32:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vNbM3-002tdf-1i for pgsql-admin@arkaria.postgresql.org; Mon, 24 Nov 2025 18:32:03 +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 1vNbM3-002tdM-0B for pgsql-admin@lists.postgresql.org; Mon, 24 Nov 2025 18:32:03 +0000 Received: from mail-oo1-xc36.google.com ([2607:f8b0:4864:20::c36]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vNbM0-001FQk-2v for pgsql-admin@lists.postgresql.org; Mon, 24 Nov 2025 18:32:02 +0000 Received: by mail-oo1-xc36.google.com with SMTP id 006d021491bc7-656b4881f55so2034225eaf.2 for ; Mon, 24 Nov 2025 10:32:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1764009119; x=1764613919; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=CD7ay4zjI9GGhEoAhlfYZc9qItmEUhsP/mUCB74nS8s=; b=lL0OXbIOIs2jg4IY+pEZ/7GSBmy/V8dfaaqo4K2SloSg2yKSrOota24KYOF2F3nVsN ezmypRmhkMc7LlA1c+87Feg9JENk7d+rbVjdpUunFUkl9IXJJv/cyvgQE8Y8B9++N/D0 yFCwOlIHfNp/IyWVWxfFlUBv6hS075STGkdTb8m3adoK4mMGH3iqX4T/NHyvOC0W8q3+ xPi+cYdE9R7uw1206YmKbjVmMIzKUgUdgEO+g2B8TK781Eao/OVtxCBY+sbrFahkXq4l +jGhSwILUo9xxC67f20zEDQPab/geLGCoCYBXK6ZFz3dBFHwx+KurJa9FrnrUd2rhBnu AC0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1764009119; x=1764613919; h=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=CD7ay4zjI9GGhEoAhlfYZc9qItmEUhsP/mUCB74nS8s=; b=iRMe6A19lVxiOzJqnPzIMqTngvMTX1tOXt4zZz0NLMxOig0N/1ZjSJfpSh8fG5kZFE zTXmDbkzrfNbOfhz/5eDdpXP224g5ZzUL7yRIpErVs6A27fEPTXcdkNiNmH+mRaZiwa+ v8IlgWcrCIOgphT7SjgsK97Z7klNpiYa6VCD3y8nPPT3UmG42QrnLOBHF8J5FarZ3HPP 4wJ/jMtruie7nYOY2FVGkJwrtfanxh5/XoW05/YiRWssxxVLJH1E58Epr0UKxb2RB4dJ Q7JCqSruMAdACjT0sG13mLqP924RJankHJf34HGk539UQIRiDyLi0mua0nX3HxSc3Ues a/lw== X-Gm-Message-State: AOJu0YyMVsZUY/N1bExy6bT9FHCgFeVFjjn/QOUAb/XsAVA7Cl0UCAB4 /FPnPABZxA5fmdm9jUb5FLmg6Fh4K5L4qrMFwJYIZ6gMMqSmdBI3e+fH2Q8+necH/4GrzpJ6TAK BgVsMRV6tMEUZ1namQC7m9NTQ/PRsyv80SA== X-Gm-Gg: ASbGncsg8CFxImZNtMBfu/2CNIVva6D5+JRskqqb/AbK2+BbcP+KaUYBmDD02AFNXdA DNSJhY5xU0Z6TaHHTuhie4nTif+OEYmQZP4K7qB9QHJC54jCMWLFmDmwCHv6odhl+CwWVjwkqtZ MACAFTVuC+Rw5hBRJDgyKzm7DTAmGgHJtFh0XPcfHpxQzVVh7D3Of2MqH48rLp5xaR/YulPD/Uu IXuDX1tSrZSBvBNkbD4BsEs9JXDgnDj1g2U4KZRZ1Ngh1zqJCCUBRdwj0o+bdmDFke0Qv29 X-Google-Smtp-Source: AGHT+IHKxGjLBUZrnV/mwulzzz1VznbhMTSEy3o9FoFhqAmK/wWNWGkvxvNF9Un5IFxhhuMP8oG1RuOHar0llxnsJnI= X-Received: by 2002:a05:6808:11cd:b0:44f:8bff:436e with SMTP id 5614622812f47-4514e659837mr58771b6e.12.1764009118872; Mon, 24 Nov 2025 10:31:58 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Mon, 24 Nov 2025 13:31:47 -0500 X-Gm-Features: AWmQ_bn8geVs177Y13qYqfvW2tejoT-W_r_A0vbPV8z90YyZieCGUGD2iZ-Qzgo Message-ID: Subject: Re: Is the pg_isready database name relevant? To: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000e9371e06445b60fe" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e9371e06445b60fe Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Nov 24, 2025 at 1:18=E2=80=AFPM David G. Johnston < david.g.johnston@gmail.com> wrote: > 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, bu= t >>>>>> pg_isready ignores nonexistent databases. >>>>>> >>>>>> Is this an application bug, a minor doc bug or am I missing somethin= g? >>>>>> >>>>> >>>>> 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 P= G >> 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 eit= her >> 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 tho= se > values to be made optional and so the current implementation is a bit of = a > hack to get around that fact. > "Option exists, is mentioned in --help, but doesn't do anything" is a (very low priority) bug. That's plain and simple. You'd say the same thing about a non-Postgresql program that you use, but you resist it in the system you're invested in. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000e9371e06445b60fe Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Nov 24, 2025 at 1:18=E2=80=AFPM D= avid G. Johnston <david.g.= johnston@gmail.com> wrote:
On Mon, Nov 24, 2025, 09:53 Ron Johnson <ronljohnsonjr@gma= il.com> 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 <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 &quo= t;-d, --dbname=3DDBNAME" option is mentioned in --help output, but pg_= isready ignores=C2=A0nonexistent=C2=A0databases.

I= s this an application bug, a minor doc bug or am I=C2=A0missing something?<= br>

It=E2=80=99s documented in = the Notes 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 people should use it to not put spurious errors into the logs.
<= /blockquote>

The person on the client s= ide isn't thinking about what's going in the PG server's logs.<= /div>

This is something that should=C2=A0be fixed= .=C2=A0 Very low priority, after the data corruption and feature bugs, and = useful new=C2=A0features added, but either return an error code if the clie= nt 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.=C2=A0 It works just fine for its intent.=C2=A0 Sure, it cou= ld be modified to also do something different.=C2=A0 But you haven't ex= plained why that would be a worthwhile use of effort.=C2=A0 All I'm see= ing it admittedly a slightly non-intuitative specification that does requir= e reading and some degree of caring on the part of the user.=C2=A0 And prob= ably some recognition that it works this way because the backend protocol d= oesn't allow for those values to be made optional and so the current im= plementation is a bit of a hack to get around that fact.

"Option exists, is mentioned in --help, but = doesn't do anything" is a (very low priority) bug.=C2=A0 That'= s plain and simple.=C2=A0

You'd say the same t= hing about a non-Postgresql program that you use, but you resist it in the = system you're invested in.

--
Death to <Redacted>, and butter sauce.
Don= 9;t boil me, I'm still alive.
<Redacted> lobster!
--000000000000e9371e06445b60fe--