On 2019-12-21 09:01, Thomas Munro wrote:
I think this problem goes away if we commit the per-object collation version patch set[1]. It drops the collversion column, and Julien's recent versions handle pg_upgrade quite well, as long as a collation by the same name exists in the target cluster. In that universe, if initdb didn't create them, we'd have to tell people to create all necessary collations manually before doing a pg_upgrade into it, and that doesn't seem great. Admittedly there might be some weird cases where a collation is somehow completely different but has the same name.
Setting this patch to Returned with Feedback. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
