| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Collation versioning |
| Date: | 2018-09-12 11:20:46 |
| Message-ID: | 0447ec7b-cdb6-7252-7943-88a4664e7bb7@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/09/2018 10:15, Christoph Berg wrote:
> Re: Thomas Munro 2018-09-07 <CAEepm=1xGTsLDx63UEdcJ8MdG63CNJ-tsDWHbH9djtvxRH5ZWw(at)mail(dot)gmail(dot)com>
>> 2. We could remove datcollate and datctype and instead store a
>> collation OID. I'm not sure what problems would come up, but for
>> starters it seems a bit weird to have a shared catalog pointing to
>> rows in a non-shared catalog.
>
> Naive idea: make that catalog shared? Collations are system-wide after
> all.
By the same argument, extensions should be shared, but they are not.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2018-09-12 11:25:48 | Re: Collation versioning |
| Previous Message | Amit Langote | 2018-09-12 10:53:39 | Re: Getting ERROR: could not open file "base/13164/t3_16388" with partition table with ON COMMIT |