| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Preserve versions of initdb-created collations in pg_upgrade |
| Date: | 2020-01-24 10:04:25 |
| Message-ID: | fa8f6460-7369-0f6b-a65d-8cc1bfdb97d9@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-01-24 10:15:54 | Re: Busted(?) optimization in ATAddForeignKeyConstraint |
| Previous Message | Juan José Santamaría Flecha | 2020-01-24 09:48:19 | Re: Allow to_date() and to_timestamp() to accept localized names |