From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | "Finnerty, Jim" <jfinnert(at)amazon(dot)com> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Daniel Verite <daniel(at)manitou-mail(dot)org> |
Subject: | Re: ICU for global collation |
Date: | 2022-01-18 03:47:13 |
Message-ID: | 20220118034713.r5cmqbgvnijywnse@jrouhaud |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Mon, Jan 17, 2022 at 07:07:38PM +0000, Finnerty, Jim wrote:
> On 10.01.22 12:49, Daniel Verite wrote:
>
> > I think some users would want their db-wide ICU collation to be
> > case/accent-insensitive.
> ...
> > IIRC, that was the context for some questions where people were
> > enquiring about db-wide ICU collations.
>
> +1. There is the DEFAULT_COLLATION_OID, which is the cluster-level default
> collation, a.k.a. the "global collation", as distinct from the "db-wide"
> database-level default collation, which controls the default type of the
> collatable types within that database.
There's no cluster-level default collation, and DEFAULT_COLLATION_OID is always
database-level (and template1 having a specific default collation). The
template0 database is there to be able to support different databases with
different default collations, among other things.
So this patchset would allow per-database default ICU collation, although not
non-deterministic ones.
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2022-01-18 03:50:46 | Re: Skipping logical replication transactions on subscriber side |
Previous Message | Amit Kapila | 2022-01-18 03:37:44 | Re: Skipping logical replication transactions on subscriber side |