| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Pgsql-Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow tailoring of ICU locales with custom rules |
| Date: | 2023-02-22 17:35:34 |
| Message-ID: | 6204a76e-c7d7-5a6a-07d2-a8af8ca16504@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 20.02.23 17:30, Daniel Verite wrote:
> - pg_dump support need to be added for CREATE COLLATION / DATABASE
I have added that.
>
> - there doesn't seem to be a way to add rules to template1.
> If someone wants to have icu rules and initial contents to their new
> databases, I think they need to create a custom template database
> (from template0) for that purpose, in addition to template1.
> From a usability standpoint, this is a bit cumbersome, as it's
> normally the role of template1.
> To improve on that, shouldn't initdb be able to create template0 with
> rules too?
Right, that would be an initdb option. Is that too many initdb options
then? It would be easy to add, if we think it's worth it.
| Attachment | Content-Type | Size |
|---|---|---|
| v6-0001-Allow-tailoring-of-ICU-locales-with-custom-rules.patch | text/plain | 36.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-02-22 17:41:52 | Re: wrong query result due to wang plan |
| Previous Message | Mark Dilger | 2023-02-22 17:27:19 | Re: Non-superuser subscription owners |