Re: BUG #15168: "pg_isready -d" effectively ignores given database name - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #15168: "pg_isready -d" effectively ignores given database name
Date
Msg-id CAKFQuwZb+XrzPJ48ZbO52Yd=oAxFrRhSTK_XXr3Z4kLoL5d8Yw@mail.gmail.com
Whole thread Raw
In response to BUG #15168: "pg_isready -d" effectively ignores given database name  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #15168: "pg_isready -d" effectively ignores given databasename
List pgsql-bugs
On Monday, April 23, 2018, PG Bug reporting form <noreply@postgresql.org> wrote:
# Not expected, database "jibberish" does not exist:
$ pg_isready -d jibberish
/run/media/jthomas/BackupOne/development/snowdrift/.postgres-work:5432 -
accepting connections

The notes section of the docs for the command cover this behavior.  It is not a bug, the utility answers whether the server will accept connections generally, not that a specific connection string and credentials are valid.

David J.

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15168: "pg_isready -d" effectively ignores given database name
Next
From: PG Bug reporting form
Date:
Subject: BUG #15169: create index CONCURRENTLY conflict with other table's COPY