Re: BUG #6053: Can't do DISTINCT on citext column

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Regina <lr(at)pcorp(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6053: Can't do DISTINCT on citext column
Date: 2011-06-16 19:42:26
Message-ID: BANLkTintSZnLactv4dDrJs1BAXyt2ugeFQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sun, Jun 5, 2011 at 3:22 PM, Regina <lr(at)pcorp(dot)us> wrote:
>
> The following bug has been logged online:
>
> Bug reference:      6053
> Logged by:          Regina
> Email address:      lr(at)pcorp(dot)us
> PostgreSQL version: 9.1beta1
> Operating system:   Windows
> Description:        Can't do DISTINCT on citext column
> Details:
>
> I have a table I created like this:
> -- With and without the COLLATE in there I get the same error.
>
>  CREATE TABLE test
> (
>  fullname citext COLLATE pg_catalog."POSIX",
> );
>
> INSERT INTO  test(fullname) VALUES('test1'),('test2');
>
> When I do a:
> SELECT DISTINCT fullname FROM test;
>
> or a
>
> SELECT DISTINCT fullname COLLATE pg_catalog."POSIX" FROM test;
>
>
> It gives error:
>
> ERROR:  could not determine which collation to use for lower() function
> HINT:  Use the COLLATE clause to set the collation explicitly.

I don't see a reply to this bug report, but I believe Tom fixed it in beta2.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2011-06-16 19:43:32 Re: BUG #6040: ODBC 64 + SSL Hangs
Previous Message Robert Haas 2011-06-16 19:40:32 Re: BUG #6054: Insert to table, which has fkey to table,which is parenttable for another table - error