| From: | "Marshall, Steve" <smarshall(at)wsi(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | CK Leung <ck(at)wecity(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: sorting problem |
| Date: | 2009-05-04 12:02:43 |
| Message-ID: | 49FED963.6030708@wsi.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Try setting the variable lc_collate, either in an individual session
using SET or (to change it for all session) in postgresql.conf. <br>
<br>
Craig Ringer wrote:
<blockquote cite="mid49FEAD6D(dot)5090201(at)postnewspapers(dot)com(dot)au" type="cite">
<pre wrap="">CK Leung wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I create a new database use UTF-8 and SQL_ASCII, same result found, how
can i fix this problem ?
</pre>
</blockquote>
<pre wrap=""><!---->
If I recall correctly, the collation order is set at initdb time, and
isn't bound to the database encoding. If that's right, you'd need to
dump all your databases, re-initdb with the new collation settings, and
re-load your databases.
--
Craig Ringer
</pre>
</blockquote>
<br>
</body>
</html>
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/html | 979 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Piergiorgio Buongiovanni | 2009-05-04 15:58:54 | BUG #4790: ENUM word not recognized! |
| Previous Message | Craig Ringer | 2009-05-04 08:55:09 | Re: sorting problem |