| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "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:20:58 |
| Message-ID: | CAKFQuwbE9BHB_T7amx30jT9Qwr=iTTfQ=4B63JAo+en4QSZ__w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thursday, October 26, 2023, PG Doc comments form <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
> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2023-10-26 12:34:24 | Re: pg_isready --dbname option is broken. So it should not be in the manual |
| Previous Message | PG Doc comments form | 2023-10-26 11:46:55 | pg_isready --dbname option is broken. So it should not be in the manual |