| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Dave Cramer' <pg(at)fastcrypt(dot)com>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "Laurenz Albe" <laurenz(dot)albe(at)cybertec(dot)at>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Jing Wang <jingwangian(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: Libpq support to connect to standby server as priority |
| Date: | 2019-01-18 00:08:45 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1FB6947A@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Dave Cramer [mailto:pg(at)fastcrypt(dot)com]
> >> 2) If there's no node on which pg_is_in_recovery() returns false,
> then
> >> we need to retry until we find it. To not retry forever, there
> >> should be a timeout counter parameter.
> Checking the code I see we actually use show transaction_read_only.
Also, does PgJDBC really repeat connection attempts for a user-specified duration? Having a quick look at the code, it seemed to try each host once in a while loop.
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2019-01-18 00:15:24 | Re: Libpq support to connect to standby server as priority |
| Previous Message | Peter Geoghegan | 2019-01-18 00:03:27 | Re: Fixing findDependentObjects()'s dependency on scan order (regressions in DROP diagnostic messages) |