Re: BUG #1996: DISTINCT fails with national character varying - Mailing list pgsql-bugs

From Ludmil Tinkov
Subject Re: BUG #1996: DISTINCT fails with national character varying
Date
Msg-id 898CCCAD9659C94EB671794CBD782F2C01282D@production.fyrex.dom
Whole thread Raw
In response to BUG #1996: DISTINCT fails with national character varying  ("Ludmil Tinkov" <ludmil@fyrex.com>)
List pgsql-bugs
Thanks, Tom!

I'll tackle this issue this weekend.=20
I'll also upgrade to PostgreSQL 8 (most probably)

Thanks once again for your comprehensive reply!

Best regards,
Ludmil Tinkov

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]=20
Sent: Tuesday, October 25, 2005 5:34 AM
To: Ludmil Tinkov
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #1996: DISTINCT fails with national character varyi=
ng=20

"Ludmil Tinkov" <ludmil@fyrex.com> writes:
> select distinct name from depression

> --the last statement returns only a single row
> --namely: =D0=90=D0=BD=D0=B0
> --it should return 4 rows!

This has been seen to happen when you select a database encoding that
does not match the encoding expected by the postmaster's LC_CTYPE locale
setting.  It's really a bug in the locale definitions, if you ask me,
but good luck getting the glibc guys to change those :-(.  In the
meantime, make sure your locale and encoding agree.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Seneca Cunningham"
Date:
Subject: BUG #1999: contrib/spi doesn't receive the configured CFLAGS
Next
From: "Telin Lin"
Date:
Subject: BUG #2001: Signal 11 after concurrent inserts + updates