Re: pgsql: Add option to use ICU as global locale provider
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christoph Berg <myon@debian.org>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
pgsql-hackers@lists.postgresql.org
Date: 2022-03-21T18:37:12Z
Lists: pgsql-hackers
Christoph Berg <myon@debian.org> writes: > A possible solution might be to rip out all the locale columns except > "Encoding" from \l, and leave them in place for \l+. I'd rather see a single column summarizing the locale situation. Perhaps it could be COALESCE(daticulocale, datcollate), or something using a CASE on datlocprovider? Then \l+ could replace that with all the underlying columns. > For \l+, I'd suggest moving the database size and the tablespace to > the front, after owner. I think it's confusing if the + and non-+ versions of a command present their columns in inconsistent orders. I'm not dead set against this, but -0.5 or so. regards, tom lane
Commits
-
psql: fix \l display for pre-v15 databases.
- 7129a9791eaf 15.0 landed
-
Fix global ICU collations for ICU < 54
- 3a671e1f7cb8 15.0 landed
-
Add option to use ICU as global locale provider
- f2553d43060e 15.0 cited
-
Add support for collation attributes on older ICU versions
- b8f9a2a69a27 12.0 cited