From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: vrms@netcologne.de
Subject: pg_isready --dbname option is broken. So it should not be in the manual
Date: Thu, 26 Oct 2023 11:46:55 +0000
Message-ID: <169832081564.1769271.15409391744737486816@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/app-pg-isready.html
Description:
the --dbname option in pg_isready seems not to work propperly. the tool
returns 'ok' as long as the cluster itselft is running, no matter how wrong
the bdname might be.
as this seems to be a ~10 year old misbehaviour as per the below thread I
think it should be removed from the manual.
https://www.postgresql.org/message-id/flat/52840D38.9070604%40agliodbs.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, vrms@netcologne.de
Subject: Re: pg_isready --dbname option is broken. So it should not be in the manual
In-Reply-To: <169832081564.1769271.15409391744737486816@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox