| 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-25 21:56:00 |
| Message-ID: | 162fece5f43.c55f9f2c21063.5048374418404228247@zoho.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thank you again. You're right that checking for database x's existence, while logged into database x, is pointless. I didn't mention that for that command I'd be using the default postgres database.
But again, you're right about what's simple/better and what's not.
In fact, just today, I discovered that there may be an even simpler solution for our scenario: have Yesod deal with postgres altogether -- no script from us. But that's outside the scope of this thread.
Back to scope: I simply vote that the '-d' option of pg_isready be deprecated in favor of a dedicated db_exists utility, rather than change existing spec, for the reasons you gave.
Jake T.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-04-25 22:19:31 | BUG #15177: handling of the US/Pacific-New timezone |
| Previous Message | PG Bug reporting form | 2018-04-25 20:16:51 | BUG #15176: ecpg generation error |