| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Kyle Spearrin <kspearrin(at)bitwarden(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | Justin Baur <jbaur(at)bitwarden(dot)com>, Vince Grassia <vgrassia(at)bitwarden(dot)com> |
| Subject: | Re: CREATE COLLATION without LOCALE throws error in v15 |
| Date: | 2022-12-07 17:44:15 |
| Message-ID: | 69598b5a07183ea8c6ec20826c1b549db1128070.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 2022-12-07 at 13:04 +0100, Peter Eisentraut wrote:
> This was an intentional change because of underlying conceptual and
> catalog changes. lc_collate, lc_ctype, and iculocale are now tracked
> separately in the catalogs. This is also important because for a
> database they actually are used separately. So this also keeps the
> locale/collation settings for databases and collations consistent.
That makes sense, but there also doesn't seem to be much harm in
supporting the old behavior where it works as long as ctype==collate.
As in my patch, it accepts either locale or ctype==collate as the icu
locale.
We can discourage relying on that by updating the documentation as you
suggest.
--
Jeff Davis
PostgreSQL Contributor Team - AWS
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-12-07 20:16:30 | BUG #17706: ALTER TYPE leads to crash |
| Previous Message | Nunya Business | 2022-12-07 15:28:28 | Re[4]: PG 14.5 -- Impossible to restore dump due to interaction/order of views, functions, and generated columns |