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

Yes,=A0 I'm definitely running 9.1.2 (on the output I sent earlier today).
I've also tried again on yet another different system and get the same bug =
there.

I do have other databases in my cluster which probably explains the differe=
nt datlastsysoid.

I am at a loss to explain what could be different.=A0 I've run it on differ=
ent machines,
different linux distros and both postgres 9.1 releases,=A0=A0 and see same =
result every time.
There must be some (other) external environmental factor.=A0=A0 Do you happ=
en to know
of any?=A0 I wonder if the locale in effect when I ran initdb affects it?
I would have had LANG=3DC and LC_ALL=3DC exported.=A0=A0=A0=A0 Do you have
any system where you could try an initdb with those environment vars export=
ed?

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

Regards,=A0=A0=A0 John Lumby
----------------------------------------

=20=09=09=20=09=20=20=20=09=09=20=20