pg_isready --dbname option is broken. So it should not be in the manual

From: PG Doc comments form <noreply(at)postgresql(dot)org>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Cc: vrms(at)netcologne(dot)de
Subject: pg_isready --dbname option is broken. So it should not be in the manual
Date: 2023-10-26 11:46:55
Message-ID: 169832081564.1769271.15409391744737486816@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

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

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message David G. Johnston 2023-10-26 12:20:58 Re: pg_isready --dbname option is broken. So it should not be in the manual
Previous Message Maxim Yablokov 2023-10-26 10:31:07 Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table