Re: [18] Policy on IMMUTABLE functions and Unicode updates
Laurenz Albe <laurenz.albe@cybertec.at>
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>, Jeff Davis <pgsql@j-davis.com>,
pgsql-hackers@postgresql.org, Daniel Verite <daniel@manitou-mail.org>,
Noah Misch <noah@leadboat.com>, Tom Lane <tgl@sss.pgh.pa.us>, Jeremy
Schneider <schneider@ardentperf.com>
Date: 2024-07-23T07:11:42Z
Lists: pgsql-hackers
On Mon, 2024-07-22 at 13:55 -0400, Robert Haas wrote: > On Mon, Jul 22, 2024 at 1:18 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote: > > I understand the difficulty (madness) of discussing every Unicode > > change. If that's unworkable, my preference would be to stick with some > > Unicode version and never modify it, ever. > > I think that's a completely non-viable way forward. Even if everyone > here voted in favor of that, five years from now there will be someone > who shows up to say "I can't use your crappy software because the > Unicode tables haven't been updated in five years, here's a patch!". > And, like, what are we going to do? Still keeping shipping the 2024 > version of Unicode four hundred years from now, assuming humanity and > civilization and PostgreSQL are still around then? Holding something > still "forever" is just never going to work. I hear you. It would be interesting to know what other RDBMS do here. Yours, Laurenz Albe