Re: pgsql: Add option to use ICU as global locale provider - Mailing list pgsql-hackers

From Christoph Berg
Subject Re: pgsql: Add option to use ICU as global locale provider
Date
Msg-id YjivDPvI9TMa5ppu@msg.df7cb.de
Whole thread Raw
In response to Re: pgsql: Add option to use ICU as global locale provider  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: pgsql: Add option to use ICU as global locale provider  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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 by date:

Previous
From: Robert Haas
Date:
Subject: Re: refactoring basebackup.c (zstd workers)
Next
From: David Christensen
Date:
Subject: Re: [PATCH] add relation and block-level filtering to pg_waldump