Re: [HACKERS] [bug fix] PG10: libpq doesn't connect to alternativehosts when some errors occur

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: [HACKERS] [bug fix] PG10: libpq doesn't connect to alternativehosts when some errors occur
Дата
Msg-id CA+TgmoZRQ+aq4WMLg9dnr6AYTtH9W6Nv9Xng_xnovixgjZ4p3g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] [bug fix] PG10: libpq doesn't connect to alternativehosts when some errors occur  (Michael Paquier <michael.paquier@gmail.com>)
Ответы Re: [HACKERS] [bug fix] PG10: libpq doesn't connect to alternativehosts when some errors occur  (Michael Paquier <michael.paquier@gmail.com>)
Список pgsql-hackers
Дерево обсуждения 
On Thu, May 18, 2017 at 7:06 AM, Michael Paquier
<michael.paquier@gmail.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

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] statement_timeout is not working as expected with postgres_fdw
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] Proposal: Improve bitmap costing for lossy pages