| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kristian Lance <kristian(dot)lance(at)crc(dot)ca> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Solved: SQL Query Problem |
| Date: | 2002-10-23 18:35:12 |
| Message-ID: | 3041.1035398112@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Kristian Lance <kristian(dot)lance(at)crc(dot)ca> writes:
> This message is a follow up to this thread:
> http://archives.postgresql.org/pgsql-bugs/2001-12/msg00008.php
> I finally got a chance to rebuild the DB server using C locale, and it made
> no difference to my ORDER BY problem. PostgreSQL did not distinguish
> between slashes, dashes, and spaces when sorting the records.
I don't believe you did it right then :-(. That sure sounds like a
locale-driven behavior. Try examining the pg_control file with
contrib/pg_controldata to confirm for certain what the collation is.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-10-23 19:07:21 | Re: Bug #803: Problem with timestamp conversion |
| Previous Message | pgsql-bugs | 2002-10-23 17:32:35 | Bug #803: Problem with timestamp conversion |