| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Collation and primary keys |
| Date: | 2025-07-17 18:59:14 |
| Message-ID: | 6b7d402f4516b0a71786dec2fe9266708c73ae38.camel@j-davis.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
> 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.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2025-07-17 19:37:31 | Re: Returning nbtree posting list TIDs in DESC order during backwards scans |
| Previous Message | Robert Treat | 2025-07-17 18:58:20 | Re: small fix for pg_overexplain docs |