pgsql: Go back to using a separate method for doing ILIKE for single

From: adunstan(at)postgresql(dot)org (Andrew Dunstan)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Go back to using a separate method for doing ILIKE for single
Date: 2007-09-22 03:58:34
Message-ID: 20070922035834.CB56F753E4C@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2007-09-22 04:37:53 pgsql: Doh --- what's really happening on buildfarm member grebe is that
Previous Message Tom Lane 2007-09-22 00:36:38 pgsql: Fix varlena.c routines to allow 1-byte-header text values.