Re: pgsql: Add option to use ICU as global locale provider
| От | Tom Lane |
|---|---|
| Тема | Re: pgsql: Add option to use ICU as global locale provider |
| Дата | |
| Msg-id | 2158266.1647887832@sss.pgh.pa.us обсуждение |
| Ответ на | Re: pgsql: Add option to use ICU as global locale provider (Christoph Berg <myon@debian.org>) |
| Ответы |
psql -l and locales (Re: pgsql: Add option to use ICU as global locale provider)
|
| Список | 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
В списке pgsql-hackers по дате отправления: