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

On Thursday, October 26, 2023, Daniel Gustafsson wrote: > > On 26 Oct 2023, at 14:20, David G. Johnston > wrote: > > > > On Thursday, October 26, 2023, PG Doc comments form < > nore...@postgresql.org > wrote: > > The following documentation comment has been logged

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

> On 26 Oct 2023, at 14:20, David G. Johnston > wrote: > > On Thursday, October 26, 2023, PG Doc comments form > wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/app-pg-isready.html >

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

On Thursday, October 26, 2023, PG Doc comments form 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 'o

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

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 bdn