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

From Daniel Gustafsson
Subject Re: pg_isready --dbname option is broken. So it should not be in the manual
Date
Msg-id 27E42B9D-59F4-4DF7-9D78-4C3A49FF472E@yesql.se
Whole thread Raw
In response to Re: pg_isready --dbname option is broken. So it should not be in the manual  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: pg_isready --dbname option is broken. So it should not be in the manual
List pgsql-docs
> On 26 Oct 2023, at 14:20, David G. Johnston <david.g.johnston@gmail.com> wrote:
>
> On Thursday, October 26, 2023, PG Doc comments form <noreply@postgresql.org <mailto: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 <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
<https://www.postgresql.org/message-id/flat/52840D38.9070604%40agliodbs.com>
>
> Read the notes section.

The notes section is pretty hidden though, I can sympathize with anyone missing
it and maybe making the info a bit more visible would be good?

--
Daniel Gustafsson




pgsql-docs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: pg_isready --dbname option is broken. So it should not be in the manual
Next
From: "David G. Johnston"
Date:
Subject: Re: pg_isready --dbname option is broken. So it should not be in the manual