Re: BUG #15168: "pg_isready -d" effectively ignores given databasename

Поиск
Список
Период
Сортировка
От jake
Тема Re: BUG #15168: "pg_isready -d" effectively ignores given databasename
Дата
Msg-id 162f93f6c75.cdd696776295.5991878161692757736@zoho.com
обсуждение исходный текст
Ответ на Re: BUG #15168: "pg_isready -d" effectively ignores given database name  ("David G. Johnston" <david.g.johnston@gmail.com>)
Ответы Re: BUG #15168: "pg_isready -d" effectively ignores given databasename  (jake <jakelist@zoho.com>)
Список pgsql-bugs
Дерево обсуждения
Ah-ha. Thank you for pointing that out. I did not notice.

In case you're interested, I used a StackOverflow solution to programmatically determine whether a database exists, after first ensuring that the cluster has been initialized and that the server is running.

Thank you for your rapid response,
Jake
---- On Mon, 23 Apr 2018 21:29:11 -0700 David G. Johnston <david.g.johnston@gmail.com> wrote ----

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 по дате отправления:

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #15171: JDBC TIMESTAMP WITH TIME ZONE PSQLException When UsingSubstitution Parameter
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #15170: PQtransactionStatus returns ACTIVE after Empty Commit