Re: Collation and primary keys

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Collation and primary keys
Date: 2025-07-17 21:35:00
Message-ID: cf178a6176a3b894be687bb6d1ea369463c2a4f9.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2025-07-17 at 11:59 -0700, Jeff Davis wrote:
> On Thu, 2025-07-17 at 08:30 +0200, Laurenz Albe wrote:
> > I wasn't aware how Oracle handles case mapping, but it seems you
> > are right:
>
> How does it handle UPPER('ß')? If the result is 'ß', that means it's
> similar to the builtin C.UTF-8. If the result is 'SS', that means it's
> similar to PG_UNICODE_FAST.

It returns 'ß'.

> > I'm still a little bit worried that changes in the case mapping might
> > break some indexes.  We have a track record with going against the
> > standard when it comes to case conversion, so perhaps we wouldn't
> > spill too much milk if we only convert ASCII correctly.
> >
> > But perhaps I am just being paranoid.
>
> That's a reasonable concern, and I don't mean to dismiss it. But I
> believe that problem is two orders of magnitude smaller than the
> problems we have with the status quo.

I agree with that.

Yours,
Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-07-17 23:16:29 Re: Log prefix missing for subscriber log messages received from publisher
Previous Message Nathan Bossart 2025-07-17 21:34:16 Re: [PATCH] Add tests for binaryheap.c