| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Jeremy Schneider <schneider(at)ardentperf(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Jim Nasby <nasbyj(at)amazon(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Collation version tracking for macOS |
| Date: | 2022-06-09 18:36:37 |
| Message-ID: | CAH2-Wzn_WEjnOrSus6LPHuJYhdehQNzZ=CkhNMpMfCc3Q8-WdA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 9, 2022 at 10:54 AM Jeremy Schneider
<schneider(at)ardentperf(dot)com> wrote:
> MySQL did the right thing here by doing what every other RDBMS did, and just making a simple “good-enough” collation hardcoded in the DB, same across all platforms, that never changes.
That's not true. Both SQL Server and DB2 have some notion of
collations that are versioned.
Oracle may not, but then Oracle also handles collations by indexing
strxfrm() blobs, with all of the obvious downsides that that entails
(far larger indexes, issues with index-only scans). That seems like an
excellent example of what not to do.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2022-06-09 18:46:02 | Re: Checking for missing heap/index files |
| Previous Message | Ma, Marcus | 2022-06-09 18:36:21 | Sharing DSA pointer between parallel workers after they've been created |