Re: Locale, encoding, sort order confusion

From: John Gunther <postgresql(at)bucksvsbytes(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Locale, encoding, sort order confusion
Date: 2006-08-21 16:51:27
Message-ID: 44E9E48F.90909@bucksvsbytes.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Alvaro Herrera wrote:
<blockquote cite="mid20060821001057(dot)GB1130(at)alvh(dot)no-ip(dot)org" type="cite">
<blockquote type="cite">
<pre wrap="">For example, with all LC_* parameters set to "en_US.UTF8", I get the
following incorrect "order:by":

B&eacute;arn
B&eacute;cancour
Beaupr&eacute;
</pre>
</blockquote>
<pre wrap=""><!---->
Did you initdb with locale en_US.UTF8, and also createdb with encoding
UTF8? While you can certainly choose mismatching values in createdb and
initdb, you shouldn't because it doesn't work.</pre>
</blockquote>
That's an interesting question. Are the LC_* variables set by initdb or
createdb? In other words, does their value indicate what initdb
settings I used? If I do a default createdb, will the new database
automatically be consistent with the cluster's initdb?<br>
</body>
</html>

Attachment Content-Type Size
unknown_filename text/html 1.0 KB

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2006-08-21 16:58:45 Re: cannot open pg_database
Previous Message Alban Hertroys 2006-08-21 16:47:51 Queries joining views