| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [bug fix] PG10: libpq doesn't connect to alternative hosts when some errors occur |
| Date: | 2017-05-18 14:30:38 |
| Message-ID: | CA+TgmoZRQ+aq4WMLg9dnr6AYTtH9W6Nv9Xng_xnovixgjZ4p3g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 18, 2017 at 7:06 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> FWIW, I am of the opinion to not have an implementation based on any
> SQLSTATE codes, as well as not doing something similar to JDBC.
> Keeping things simple is one reason, a second is that the approach
> taken by libpq is correct at its root.
Because why?
I was initially on the same side as you and Tom, but now I'm really
wavering. What good is a feature that's supposed to find you a usable
connection if it sometimes decides not to find one?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-05-18 14:37:33 | Re: Proposal: Improve bitmap costing for lossy pages |
| Previous Message | Robert Haas | 2017-05-18 14:26:51 | Re: statement_timeout is not working as expected with postgres_fdw |