From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
---|---|
To: | Christoph Berg <myon(at)debian(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Collation versioning |
Date: | 2018-09-05 21:18:31 |
Message-ID: | CAEepm=3mKYhXS9NQCsPkGhkQxKAeZwbDneZV7QYKTDDYstTxZA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 5, 2018 at 12:10 PM Christoph Berg <myon(at)debian(dot)org> wrote:
> > So, it's not ideal but perhaps worth considering on the grounds that
> > it's better than nothing?
>
> Ack.
Ok, here's a little patch like that.
postgres=# select collname, collcollate, collversion from pg_collation
where collname = 'en_NZ';
collname | collcollate | collversion
----------+-------------+-------------
en_NZ | en_NZ.utf8 | 2.24
(1 row)
--
Thomas Munro
http://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
0001-Set-collversion-for-collations-that-come-from-glibc.patch | application/octet-stream | 3.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Victor Spirin | 2018-09-05 21:25:28 | Re: PostgreSQL does not start when max_files_per_process> 1200 on Windows 7 |
Previous Message | Chapman Flack | 2018-09-05 21:09:59 | *_to_xml() should copy SPI_processed/SPI_tuptable |