| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Pgsql-Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ICU for global collation |
| Date: | 2022-01-10 15:14:31 |
| Message-ID: | YdxNVzIN8rwklXsE@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 10, 2022 at 03:45:47PM +0100, Daniel Verite wrote:
>
> By that I understand that CREATE DATABASE is limited to copying a template
> database and then not write anything into it beyond that, as it's
> not even connected to it.
Yes.
> I guess there's still the possibility of requiring that the ICU db-wide
> collation of the new database does exist in the template database,
> and then the CREATE DATABASE would refer to that collation instead of
> an independent locale string.
That could work. However if having the collation in the template database a
strict requirement the something should also be done for initdb, and it will
probably be a bigger problem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-01-10 15:15:00 | Re: Undocumented behavior of timezone(zone, timestamp) for impossible timestamptz's |
| Previous Message | Andrew Dunstan | 2022-01-10 15:14:10 | Re: Fix vcregress plpython3 warning |