pgsql: Go back to using a separate method for doing ILIKE for single - Mailing list pgsql-committers

From adunstan@postgresql.org (Andrew Dunstan)
Subject pgsql: Go back to using a separate method for doing ILIKE for single
Date
Msg-id 20070922035834.CB56F753E4C@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Go back to using a separate method for doing ILIKE for single byte
character encodings that doesn't involve calling lower(). This should
cure the performance regression in this case complained of by Guillaume
Smet. It still leaves the horrid performance for multi-byte encodings
introduced in 8.2, but there's no obvious solution for that in sight.

Modified Files:
--------------
    pgsql/src/backend/utils/adt:
        like.c (r1.70 -> r1.71)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/like.c?r1=1.70&r2=1.71)
        like_match.c (r1.17 -> r1.18)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/like_match.c?r1=1.17&r2=1.18)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix varlena.c routines to allow 1-byte-header text values.
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Doh --- what's really happening on buildfarm member grebe is that