| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Don Seiler <don(at)seiler(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Mixed Locales and Upgrading |
| Date: | 2020-04-08 07:32:22 |
| Message-ID: | 067adeb6-c601-7c97-9020-af6235d1757d@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2020-04-07 18:41, Don Seiler wrote:
> Follow-up question, the locale setting on the host would still be set to
> en_US (as would the postgres and template0 databases). Should I look to
> change that locale on the system to en_US.UTF-8, or even just for the
> postgres user that the DB cluster runs as? What are the ramification for
> doing (or not doing) so?
I think the only place where this would really matter is that psql by
default sets the client encoding based on the current OS locale setting.
So if you don't change the setting to en_US.UTF-8, then you might get
encoding errors when selecting data that is not representable as LATIN1
or whatever. However, if you change the setting, that doesn't mean your
terminal setup will actually display Unicode correctly. You said you're
dealing with mostly ASCII-ish data anyway, so it will probably not make
a difference.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2020-04-08 07:39:15 | Re: Estimated resources for a 500 connections instance (VM) |
| Previous Message | Michael Paquier | 2020-04-08 02:29:30 | Re: Using of --data-checksums |