Re: pg_isready --dbname option is broken. So it should not be in the manual - Mailing list pgsql-docs

From David G. Johnston
Subject Re: pg_isready --dbname option is broken. So it should not be in the manual
Date
Msg-id CAKFQuwbE9BHB_T7amx30jT9Qwr=iTTfQ=4B63JAo+en4QSZ__w@mail.gmail.com
Whole thread Raw
In response to pg_isready --dbname option is broken. So it should not be in the manual  (PG Doc comments form <noreply@postgresql.org>)
Responses Re: pg_isready --dbname option is broken. So it should not be in the manual
List pgsql-docs
On Thursday, October 26, 2023, PG Doc comments form <noreply@postgresql.org> wrote:
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

Read the notes section.

David J.
 

pgsql-docs by date:

Previous
From: PG Doc comments form
Date:
Subject: pg_isready --dbname option is broken. So it should not be in the manual
Next
From: Daniel Gustafsson
Date:
Subject: Re: pg_isready --dbname option is broken. So it should not be in the manual