On 1/11/17 3:35 PM, Petr Jelinek wrote: > On 11/01/17 18:27, Peter Eisentraut wrote: >> On 1/11/17 3:11 AM, Petr Jelinek wrote: >>> That will not help, issue is that we consider names for origins to be >>> unique across cluster while subscription names are per database so if >>> there is origin per subscription (which there has to be) it will always >>> clash if we just use the name. I already have locally changed this to >>> pg_<subscription_oid> naming scheme and it works fine. >> >> How will that make it unique across the cluster? >> >> Should we include the system ID from pg_control? >> > > pg_subscription is shared catalog so oids are unique.
Oh, I see what you mean by cluster now. It's a confusing term. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
