From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "vrms(at)netcologne(dot)de" <vrms(at)netcologne(dot)de>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_isready --dbname option is broken. So it should not be in the manual |
Date: | 2023-10-26 12:34:24 |
Message-ID: | 27E42B9D-59F4-4DF7-9D78-4C3A49FF472E@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
> On 26 Oct 2023, at 14:20, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> On Thursday, October 26, 2023, PG Doc comments form <noreply(at)postgresql(dot)org <mailto:noreply(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2023-10-26 12:59:25 | Re: pg_isready --dbname option is broken. So it should not be in the manual |
Previous 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 |