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-13 19:04:02
Message-ID: 6900.1323803042@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:
> I do have other databases in my cluster which probably explains the different datlastsysoid.

No, it wouldn't. datlastsysoid only counts objects created during
initdb.

[ thinks for a bit ] The most likely explanation for the different
datlastsysoid value is that the number of pre-created pg_collation
entries is quite a bit different on my box than yours, as a result of a
different list from "locale -a". It's hard to see why that would have
anything to do with your issue, but I have a feeling it does somehow.

What platforms have you tried this on, exactly? I tried it on Fedora 14.

> What are the values of relevant locale-type env vars when you ran initdb on your test sys?

Shrug ... C. That's my normal working environment. I did try it with
en_US.utf8 too, just for grins.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Guillaume Lelarge 2011-12-13 20:12:57 Re: BUG #6333: pgAdmin 14.1 - Listbox stupidities
Previous Message John Lumby 2011-12-13 18:35:59 Re: LIKE predicate and ERROR: 42P22: could not determine which collation to use for string comparison - HINT: Use the COLLATE clause ...