Re: unicode searches failing that use % and LIKE operators - Mailing list pgsql-general

From Benjamin Weaver
Subject Re: unicode searches failing that use % and LIKE operators
Date
Msg-id 20071023092914.B1994EB04D@webmail221.herald.ox.ac.uk
Whole thread Raw
In response to Re: unicode searches failing that use % and LIKE operators  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Thanks, Tom and Greg, for all your help.  I agree that Redhat 9 is a bit
creaky and that we here should upgrade.  In the meantime I will put together a
tiny test case that will reproduce the problem (at least on my platform).

Ben

In message <26870.1193091184@sss.pgh.pa.us> Tom Lane <tgl@sss.pgh.pa.us>
writes:
> Benjamin Weaver <benjamin.weaver@classics.ox.ac.uk> writes:
> > I AM in fact running the db on Linux.  Redhat 9.  Are the encoding
parameters
> > wrong for Linux?
>
> Hmm ... RH 9 is awfully old.  It's at least conceivable that you're
> getting bit by some glibc bug.  However, if these are just plain LIKE
> calls and not ILIKE then I don't think that theory is very viable
> --- AFAICS the regular LIKE code doesn't depend on anything from the
> platform.
>
> A slightly more viable theory is that you're getting bit by a gcc bug.
> Did you build the Postgres executables in-house, and if not where did
> you get them from?  It might be helpful if you'd show us the output
> of "pg_config".
>
> Again, if you could put together a self-contained test case (preferably
> a short psql script) it would be helpful so we could try the case on
> other machines.  It's not at all clear at this point whether the bug
> is Postgres' fault or something about the underlying platform.
>
>             regards, tom lane

--
Benjamin Weaver
Faculty Research Associate, Imaging Papyri Projects, Herculaneum Society,
Oxford
email:  benjamin.weaver@classics.ox.ac.uk
phone:  (0)1865 610236


pgsql-general by date:

Previous
From: Shane Ambler
Date:
Subject: Re: How to transfer from place to plase without backup/restore
Next
From: "Sergey Konoplev"
Date:
Subject: Re: pg_cancel_backend() does not work with buzz queries