On Thu, Oct 29, 2015 at 8:29 PM, Peter Eisentraut <pete...@gmx.net> wrote: > On 10/28/15 4:18 AM, Victor Wagner wrote: >> On Mon, 26 Oct 2015 16:25:57 -0400 >> Peter Eisentraut <pete...@gmx.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. > > There are multiple types of PostgreSQL replication, and there will be > others in the future.
That's true, but doesn't allowing every parameter to be multiply specified greatly increase the implementation complexity for a pretty marginal benefit? I think host and IP would hit 98% of the use cases here. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
