Re: hostorder and failover_timeout for libpq - Mailing list pgsql-hackers

From Surafel Temesgen
Subject Re: hostorder and failover_timeout for libpq
Date
Msg-id CALAY4q_MKXcY+wfQBMqjbK2wkgMsYsf0F340BkJFFzMtrYLoGw@mail.gmail.com
Whole thread Raw
In response to hostorder and failover_timeout for libpq  (Ildar Musin <i.musin@postgrespro.ru>)
Responses Re: hostorder and failover_timeout for libpq  (Ildar Musin <ildar@adeven.com>)
List 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


pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Avoid extra Sort nodes between WindowAggs when sorting can bereused
Next
From: Etsuro Fujita
Date:
Subject: Re: Problem while updating a foreign table pointing to a partitionedtable on foreign server