| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Michael Paquier' <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "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 06:42:21 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1F6FA5DE@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Michael Paquier [mailto:michael(dot)paquier(at)gmail(dot)com]
> Does JDBC use something like that to make a difference between a failure
> and a move-on-to-next-one?
No, it just tries the next host. See the first while loop in org/postgresql/jdbc/core/v3/ConnectionFactoryImpl.java.
> From maintenance point of view, this would
> require lookups each time a new SQLSTATE is added. Not sure that people
> would remember that.
Yes, I have the same concern, but I'll see if there's a good way anyway (e.g. whether we can simply use the class code of the SQLSTATE, which seems hopeless.) I guess PgJDBC's way is practical and sensible in the end.
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2017-05-18 06:45:36 | Re: [Proposal] Allow users to specify multiple tables in VACUUM commands |
| Previous Message | Heikki Linnakangas | 2017-05-18 06:37:45 | Re: Removal of plaintext password type references |