Re: new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII)

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: mailinglist(at)tdeo(dot)fr
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII)
Date: 2010-09-13 10:16:21
Message-ID: 4C8DF9F5.7050003@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Carlos Henrique Reimer 2010-09-13 10:16:34 Re: User function canceling VACUUMDB utility
Previous Message Mikko Partio 2010-09-13 09:25:10 Re: Incrementally Updated Backups