From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Victor Wagner <vitus(at)wagner(dot)pp(dot)ru> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Proposal: Implement failover on libpq connect level. |
Date: | 2015-08-19 18:11:31 |
Message-ID: | 15172.1440007891@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
Victor Wagner <vitus(at)wagner(dot)pp(dot)ru> writes:
> On 2015.08.20 at 00:17:35 +0900, Tatsuo Ishii wrote:
>> One downside of this is, if one of the standby servers is not
>> responding, every time clients will be blocked by the server before
>> giving up the connection trial. This could last for hours (for
> This shouldn't happen. My proposal was to connect all servers
> simultaneously, and then use that connection which would be established
> first closing other ones
That seems like seriously unfriendly behavior. It will trigger dropped
connection bleats in the server logs, not to mentioned wasted process
forks.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-08-19 19:33:23 | Re: proposal: function parse_ident |
Previous Message | jacques klein | 2015-08-19 17:45:47 | Re: how to write/setup a C trigger function in a background worker |
From | Date | Subject | |
---|---|---|---|
Next Message | rcohen | 2015-08-19 18:16:39 | Re: sql type reported for enum |
Previous Message | Victor Wagner | 2015-08-19 17:34:48 | Re: Proposal: Implement failover on libpq connect level. |