Thank you :) I'll try restarting postgresql during our next maintenance
window and report back.
--cnemelka
On Mon, Sep 9, 2019 at 3:08 PM Tom Lane wrote:
> "Daniel Verite" writes:
> > I can reproduce this by creating a new locale *after* starting
> > PostgreSQL and trying to use it before a re
"Daniel Verite" writes:
> I can reproduce this by creating a new locale *after* starting
> PostgreSQL and trying to use it before a restart.
That is interesting. I think it must mean that glibc's setlocale()
and newlocale() maintain some kind of internal cache about available
locales ... and the
Cory Nemelka wrote:
> ERROR: 22023: could not create locale "fr_FR.utf8": No such file or
> directory
> DETAIL: The operating system could not find any locale data for the locale
> name "fr_FR.utf8".
> LOCATION: report_newlocale_failure, pg_locale.c:1312
I can reproduce this by creatin
Cory Nemelka writes:
> Here is encoding for existing database:
> List of databases
> ┌───┬──┬──┬─┬─┬───┐
> │ Name│ Owner │ Encoding │ Collate │Ctype│ Access
> privileges │
Here is encoding for existing database:
List of databases
┌───┬──┬──┬─┬─┬───┐
│ Name│ Owner │ Encoding │ Collate │Ctype│ Access
privileges │
├───┼──┼───
We have already run pg_import_system_collations('pg_catalog')
--cnemelka
On Mon, Sep 9, 2019 at 12:43 PM Cory Nemelka wrote:
> We are having issues with some databases getting our locales generated.
> We are using Ubuntu 18.04 and postgresql 10.8.
>
> Example:
>
> *from bash prompt:*
>
> $ loca
We are having issues with some databases getting our locales generated. We
are using Ubuntu 18.04 and postgresql 10.8.
Example:
*from bash prompt:*
$ locale -a | egrep fr
fr_BE
fr_BE@euro
fr_BE.iso88591
fr_BE.iso885915@euro
fr_BE.utf8
fr_CA
fr_CA.iso88591
fr_CA.utf8
fr_CH
fr_CH.iso88591
fr_CH.u
