| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Add option to use ICU as global locale provider |
| Date: | 2022-03-21 16:59:56 |
| Message-ID: | YjivDPvI9TMa5ppu@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-03-21 18:37:12 | Re: pgsql: Add option to use ICU as global locale provider |
| Previous Message | Tom Lane | 2022-03-21 16:22:33 | pgsql: Fix risk of deadlock failure while dropping a partitioned index. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Christensen | 2022-03-21 17:14:19 | Re: [PATCH] add relation and block-level filtering to pg_waldump |
| Previous Message | Robert Haas | 2022-03-21 16:57:36 | Re: refactoring basebackup.c (zstd workers) |