Skip site navigation (1) Skip section navigation (2)

Re: encoding issue with postgres 8.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kailash Vyas <kailash(dot)vyas(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org, pankaj(at)interlink-marketing(dot)net
Subject: Re: encoding issue with postgres 8.0
Date: 2005-08-23 14:20:00
Message-ID: 2130.1124806800@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
Kailash Vyas <kailash(dot)vyas(at)gmail(dot)com> writes:
> The database cluster will be initialized with locale en_GB.UTF-8.
> initdb: warning: encoding mismatch
> The encoding you selected (SQL_ASCII) and the encoding that the selected
> locale uses (UTF-8) are not known to match. This may lead to
> misbehavior in various character string processing functions. To fix
> this situation, rerun initdb and either do not specify an encoding
> explicitly, or choose a matching combination.

> what is the matching locale that i should be using in this case?

If you want to use SQL_ASCII (ie, have no enforcement of encoding
validity) the only really safe locale is "C".  If you were using another
combination with your old database and not having trouble, you may
decide to ignore the warning and keep using that combination --- it'll
work just as well or badly as before.  But with what you have here,
if you ever accidentally put any non-UTF8 data into the database,
you'll likely get odd behavior.

			regards, tom lane

In response to

pgsql-admin by date

Next:From: Don DrakeDate: 2005-08-23 14:42:27
Subject: Re: sleep?
Previous:From: Gaetano MendolaDate: 2005-08-23 12:23:25
Subject: Re: Creating tables...not a usual question (I think)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group