From: | jake <jakelist(at)zoho(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #15168: "pg_isready -d" effectively ignores given database name |
Date: | 2018-04-24 20:01:46 |
Message-ID: | 162f93f6c75.cdd696776295.5991878161692757736@zoho.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)g(dot)johnston(at)gmail(dot)com> wrote ----
On Monday, April 23, 2018, PG Bug reporting form <noreply(at)postgresql(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-04-24 23:10:22 | Re: BUG #15170: PQtransactionStatus returns ACTIVE after Empty Commit |
Previous Message | PG Bug reporting form | 2018-04-24 17:59:02 | BUG #15171: JDBC TIMESTAMP WITH TIME ZONE PSQLException When Using Substitution Parameter |