Re: pg_isready docs doesn't specify what exactly it is checking
| От | Anatoli Babenia |
|---|---|
| Тема | Re: pg_isready docs doesn't specify what exactly it is checking |
| Дата | |
| Msg-id | CAK=cShjQnZfusE5rYv-y=ULpwGAj-zt3E+Ufe2kD8D4zCZ+RRw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: pg_isready docs doesn't specify what exactly it is checking ("Euler Taveira" <euler@eulerto.com>) |
| Список | pgsql-docs |
On Fri, 7 Jan 2022 at 03:29, Euler Taveira <euler@eulerto.com> wrote:
On Tue, Jan 4, 2022, at 3:11 PM, PG Doc comments form wrote:We could include a sentence explaining that a port probe is not a sufficientcondition to successfully connect to a Postgres server because the statemachine has more than 2 states. PQping [1] already states "reports the statusof the server" and describe each state it provides. Feel free to suggest animprovement to documentation.
A diagram of the state machine would be very useful.
There is no known issues with pg_isready and that report isn't clear. He says"database and/or user wasn't available". What's the exact error message? Ifthere is a reproducible test case, share it here.
PostgreSQL docker image can run initialization scripts at container start to
create database, users and maybe load some data. So when pg_isready
reports success, the DB can still be in an inconsistent state for an app to start
using it.
--
Anatoli Babenia
В списке pgsql-docs по дате отправления: