First of all, I wish to thank all the participants of the discussion for their useful suggestions and critics.
I see that people are really interested in this feature. Now, list of syntax and behavior changes against original proposal: 1. There is similar feature in JDBC, so syntax of URL-style connect string should be compatible with JDBC: postgresql://host:port,host:port/dbname... 2. In the param=value style connect string, there should be way to specify different non-standard port for each host in the cluster. So on, it seems that people came to conclusion, that allowing host:port syntax as value of the host parameter shouldn't break anything. So, port should be determined following way: If there is :portnumber in the host string, this portnumber takes precedence over anything else for this particular host. To avoid problems with file system objects with strange names, colon is interpreted as port number separator only if value of the host parameter doesn't begin with slash. If it begins with slash, it is handled exactly as it handled now. If port is not explicitly specified in the host string, then use parameter port= (for all hosts, which are not accompanied with own port number), if no port parameter in the connect string, use same chain of fallbacks up to compiled in standard value, as in use now. 3. Simultaneous connection to all the hosts in cluster shouldn't be default. By default hosts should be tried in order they are specified in the connect string. To minimize syntax changes there should be single parameter 'hostorder' which specifies order of hosts with possible choices sequential(default), parallel and random. 4. There should be a way to allow cluster software or system administrator some time to perform failover procedures and promote one of standbys to master. So, there should be additional parameter, failover_timeout, which specifies number of seconds connection attempts should be retried, if no usable master server found. 5. Parameter readonly (which allows to distinguish between failover and load balancing of readonly clients) should be implemented as in original proposal. -- Victor Wagner <vi...@wagner.pp.ru> -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers