Why there is no Unicode as option during initdb. There are some encodings,
but not all alisted in PostgreSQL manual ? How different SQL ASCII is from
Unicode ?
----- Original Message -----
From: "Tom Lane" <tgl@xxxxxxxxxxxxx>
To: "Zlatko Matić" <zlatko.matic1@xxxxxxxxxxx>
Cc: <pgsql-general@xxxxxxxxxxxxxx>
Sent: Friday, July 29, 2005 4:21 PM
Subject: Re: templates, encoding
=?iso-8859-2?Q?Zlatko_Mati=E6?= <zlatko.matic1@xxxxxxxxxxx> writes:
My template0 and template1 have SQL ASCII encoding, while I created a =
database with UNICODE encoding.
Could it cause some conflicts ? If so, how can I change templates =
databases to be UNICODE as well ?
The real question is whether the database's locale setting is compatible
with Unicode (utf-8). If not, you're going to see some problems with
comparing and sorting non-ASCII characters.
initdb is the only way to fix a bad choice of locale, unfortunately.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
