Re: LIKE predicate and ERROR: 42P22: could not determine which collation to use for string comparison - HINT: Use the COLLATE clause ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John Lumby <johnlumby(at)hotmail(dot)com>
Cc: pgsql bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: LIKE predicate and ERROR: 42P22: could not determine which collation to use for string comparison - HINT: Use the COLLATE clause ...
Date: 2011-12-12 21:38:53
Message-ID: 12191.1323725933@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

John Lumby <johnlumby(at)hotmail(dot)com> writes:
> Sorry about that, here is a script to demonstrate using a much simpler example.
> It presumes linux and that there is a bash shell at /bin/bash.

> You should see table created and loaded (takes a few minutes), then successful query explain and run,
> then create index and re-run the explain (now uses index) and query (now fails)

Hmm ... I tried this script on both HEAD and 9.1, and see no failure.
Possibly it requires some non-default configuration setting to show
the problem? Also, are you certain your database is ending up with
LC_COLLATE and LC_CTYPE set to "C"? I am not sure that createdb pays
attention to those as locale settings.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Craig Ringer 2011-12-13 00:26:08 Re: BUG #6331: Cross compile error/aborts. Works if '--disable-spinlock' is used
Previous Message Cihan ŞENGÜL 2011-12-12 15:10:02 Re: About Wince App