On 1/18/17 10:43 AM, Tom Lane wrote: > Maybe an appropriate fix would be to ignore collations whose names aren't > equal to what we get for collcollate/collctype. Presumably the latter > are getting canonicalized somehow.
Yeah, it's supposed to do that. Note that the second call to CollationCreate() in pg_import_system_collations() has the "if not exists" argument true regardless. So the error appears to come from the first one. What's fishy about this is that I can't reproduce it locally in a variety of VMs, and the buildfarm is not unanimous either. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers