Re: Change collate postgresql

From: marcelo mendoza <jmarcelo(dot)mendoza(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-novice(at)postgresql(dot)org
Subject: Re: Change collate postgresql
Date: 2020-08-20 15:54:15
Message-ID: CAPSkOeVgP=z2Cxsv-qpLMgF26X5DzcFHaWwjKMVJqTVwLBW-Ww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

In any case, could it be left like this or is the recommendation to perform
the update?

Regards

El mié., 19 ago. 2020 a las 9:56, Tom Lane (<tgl(at)sss(dot)pgh(dot)pa(dot)us>) escribió:

> marcelo mendoza <jmarcelo(dot)mendoza(at)gmail(dot)com> writes:
> > Hi Laurenz, this is the space en_US.UTF- 8 (the space is before the 8)
> > Collate | en_US.UTF-
> > | 8
> > The database was created in this way, without error, how can I fix this?
>
> I'm guessing that you specified LC_COLLATE that way when you created
> the database. Postgres won't complain if setlocale() doesn't, which
> it very possibly wouldn't.
>
> I don't believe we offer any DDL command to change that, so a direct
> UPDATE on pg_database is the only way. Should be pretty harmless
> as long as you don't try to change the setting to a functionally
> different value.
>
> regards, tom lane
>

--
Marcelo Mendoza
(0983) 383-752

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Schlaffer, Sharon 2020-08-27 15:59:10 insert vs. copy in pgAdmin
Previous Message Tom Lane 2020-08-19 13:56:06 Re: Change collate postgresql