BUG #1695: "select distinct" makes different output

Lists: pgsql-bugs
From: "philip" <philipguo(at)yahoo(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #1695: "select distinct" makes different output
Date: 2005-06-01 00:36:09
Message-ID: 20050601003609.BD392F0AC7@svr2.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 1695
Logged by: philip
Email address: philipguo(at)yahoo(dot)com
PostgreSQL version: 8.0.3
Operating system: MS Windows XP sp1 and Linux Fedora core 3
Description: "select distinct" makes different output
Details:

Hi there,

I installed PostgreSQL 8.0.3 database system on both platforms MS Windows XP
(sp1) and Linux Fedora 3, and both databse settings are exactly the same
with the encoding set to 'UNICODE'. Both database systems are running well
except one thing so far has the different results from those two databases.
Here is a query as the example:

select distinct area from ht_booking.hotels;

The result from the database on Linux FC3 has no problem but the one on
Windows XP. The data output from the later have the duplicated rows. It
seems to make no difference with or without "distinct" key word. BUT, this
happens only under one condition: the data in that column contains chinese
characters.

Please feel free to question me if there is anything I can do to help with.
Thank you.


From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "philip" <philipguo(at)yahoo(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1695: "select distinct" makes different output
Date: 2005-06-01 15:36:04
Message-ID: 14385.1117640164@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

"philip" <philipguo(at)yahoo(dot)com> writes:
> I installed PostgreSQL 8.0.3 database system on both platforms MS Windows XP
> (sp1) and Linux Fedora 3, and both databse settings are exactly the same
> with the encoding set to 'UNICODE'.

Windows' support for UNICODE is kind of broken I'm afraid :-(. You
should use a different encoding on that platform, at least until we
figure out an end-run around the OS' limitations.

regards, tom lane