From: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
---|---|
To: | Ildar Musin <i(dot)musin(at)postgrespro(dot)ru> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Victor Wagner <v(dot)wagner(at)postgrespro(dot)ru> |
Subject: | Re: hostorder and failover_timeout for libpq |
Date: | 2018-09-14 12:03:20 |
Message-ID: | CALAY4q_MKXcY+wfQBMqjbK2wkgMsYsf0F340BkJFFzMtrYLoGw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hey ,
Here are a few comment.
+ <varlistentry id="libpq-connect-falover-timeout"
xreflabel="failover_timeout">
Here's a typo: ="libpq-connect-falover-timeout"
+ {"failover_timeout", NULL, NULL, NULL,
+ "Failover Timeout", "", 10,
Word is separated by hyphen in internalPQconninfoOption lable as a
surrounding code
+ If the value is <literal>random</literal>, the host to connect to
+ will be randomly picked from the list. It allows load balacing between
+ several cluster nodes.
I Can’t think of use case where randomly picking a node rather than in
user specified order can load balance the cluster better. Can you
explain the purpose of this feature more? And in the code I can’t see
a mechanism for preventing picking one host multiple time
By the way patch doesn’t apply cleanly I think it need a rebase
http://cfbot.cputube.org/patch_19_1631.log
Regards
Surafel
From | Date | Subject | |
---|---|---|---|
Next Message | James Keener | 2018-09-14 12:50:34 | Re: Code of Conduct plan |
Previous Message | Daniel Gustafsson | 2018-09-14 11:34:22 | Re: Avoid extra Sort nodes between WindowAggs when sorting can be reused |