Re: new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII) - Mailing list pgsql-general

From Craig Ringer
Subject Re: new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII)
Date
Msg-id 4C8DF9F5.7050003@postnewspapers.com.au
Whole thread Raw
In response to new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII)  (MailingLists <mailinglist@tdeo.fr>)
List pgsql-general
On 13/09/10 19:48, MailingLists wrote:
>  Dear all of you,
>
> I'm currently working on a centos that I manage with webmin.
> A sI try to create a DB with unicode encoding the following message is
> returned to me :
>
>
>       new encoding (UTF8) is incompatible with the encoding of the
>       template database (SQL_ASCII)
>
> After a little googling, I felt happy because the solution seems easy to
> create a new utf8 db :
> createdb -E UTF8 -T template0 myDB
>
> Unfortunately, I would like to create a default template database in UTF
> or accepting all others encoding.

You could drop template1 (the default template database) and recreate it
from template0 with a utf-8 encoding.

--
Craig Ringer

Tech-related writing: http://soapyfrogs.blogspot.com/

pgsql-general by date:

Previous
From: MailingLists
Date:
Subject: new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII)
Next
From: Carlos Henrique Reimer
Date:
Subject: Re: User function canceling VACUUMDB utility