From: | Victor Wagner <vitus(at)wagner(dot)pp(dot)ru> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Patch: Implement failover on libpq connect level. |
Date: | 2015-10-28 08:18:39 |
Message-ID: | 20151028111839.6e73c68a@fafnir |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
On Mon, 26 Oct 2015 16:25:57 -0400
Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> Also, this assumes that all the components other than host and port
> are the same. Earlier there was a discussion about why the ports
> would ever need to be different. Well, why can't the database names
> be different? I could have use for that.
Because of way postgresql replication is implemented.
This multihost feature is for clusters. Either for automatic switch
from one cluster node to another when master node fails and one of the
standbys get promoted to master, or for load balancing between hot
standby nodes.
Postgresql allows different replicas listen on different ports, because
each replica has its own postgresql conf, but repication works on the
node level, not on the database level, so all the databases from master
node would be replicated with their original names.
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Tiikkaja | 2015-10-28 09:03:18 | psql: add \pset true/false |
Previous Message | Pavel Stehule | 2015-10-28 07:58:58 | Re: [PROPOSAL] Max recursion depth in WITH Queries (Common Table Expressions) |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2015-10-29 19:29:05 | Re: Patch: Implement failover on libpq connect level. |
Previous Message | Chapman Flack | 2015-10-28 03:47:27 | more re: possible pljava / pgjdbc / pgjdbc-ng code sharing |