Re: [SOLVED] Problems with a custom LOCALE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "James B(dot) Byrne" <byrnejb(at)harte-lyne(dot)ca>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [SOLVED] Problems with a custom LOCALE
Date: 2012-12-17 16:46:43
Message-ID: 26477.1355762803@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"James B. Byrne" <byrnejb(at)harte-lyne(dot)ca> writes:
> PG::Error: ERROR: new encoding (UTF8) is incompatible with the
> encoding of the template database (LATIN1)
> HINT: Use the same encoding as in the template database, or use
> template0 as template.
> : CREATE DATABASE "hll_th_forex_development" ENCODING = 'UTF-8'

> So, I now must specify a template in the database connection, where I
> did not need to before. Furthermore, the template I must use is
> template0 because regardless of what locale initdb is run in template1
> evidently is always created with LATIN1 encoding. At lease if there
> is a way to force template1 to utf8 during initdb I now lack the
> energy to discover it.

You could use initdb's -E option, but really it ought to default to the
charmap of the locale that prevails from its environment. I suspect
there's still something wonky about your custom locale. (But man,
your description of localedef is scary.)

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Wall 2012-12-17 18:07:12 Re: PG 8.4 to 9.2 upgrade issues with ownership of large objects
Previous Message James B. Byrne 2012-12-17 16:35:34 Re: [SOLVED] Problems with a custom LOCALE