Re: pgsql: Add option to use ICU as global locale provider
Christoph Berg <myon@debian.org>
From: Christoph Berg <myon@debian.org>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2022-03-21T16:59:56Z
Lists: pgsql-hackers
Re: Peter Eisentraut > > Since the intended usage seems to be that databases should either be > > using libc, or the ICU locales, but probably not both at the same > > time, does it make sense to clutter the already very wide `psql -l` > > output with two new extra columns? > > Good point, let me think about that. A possible solution might be to rip out all the locale columns except "Encoding" from \l, and leave them in place for \l+. For \l+, I'd suggest moving the database size and the tablespace to the front, after owner. Christoph
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