psql -l and locales (Re: pgsql: Add option to use ICU as global locale provider)

From: Christoph Berg <myon(at)debian(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: psql -l and locales (Re: pgsql: Add option to use ICU as global locale provider)
Date: 2022-09-06 12:25:26
Message-ID: Yxc8NoC0chLC7bfX@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Re: Tom Lane
> Christoph Berg <myon(at)debian(dot)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.

Fwiw I still think the default psql -l output should be more concise.
Any chance to have that happen for PG15?

I can try creating a patch if it has chances of getting through.

Christoph

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Masahiko Sawada 2022-09-06 14:10:04 Re: pgsql: Add ALTER SUBSCRIPTION ... SKIP.
Previous Message John Naylor 2022-09-06 06:51:43 pgsql: Fix cplusplusscheck in vpath builds

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-09-06 12:26:55 Re: predefined role(s) for VACUUM and ANALYZE
Previous Message Robert Haas 2022-09-06 12:21:50 Re: Modernizing our GUC infrastructure