Re: pgsql: Add option to use ICU as global locale provider

Поиск
Список
Период
Сортировка
От Christoph Berg
Тема Re: pgsql: Add option to use ICU as global locale provider
Дата
Msg-id YjivDPvI9TMa5ppu@msg.df7cb.de
обсуждение исходный текст
Ответ на Re: pgsql: Add option to use ICU as global locale provider  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Ответы Re: pgsql: Add option to use ICU as global locale provider  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: refactoring basebackup.c (zstd workers)
Следующее
От: David Christensen
Дата:
Сообщение: Re: [PATCH] add relation and block-level filtering to pg_waldump