Locale vs LIKE

From: "Stephen Denne" <Stephen(dot)Denne(at)datamail(dot)co(dot)nz>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Locale vs LIKE
Date: 2008-02-13 03:41:26
Message-ID: F0238EBA67824444BC1CB4700960CB4804A4F51C@dmpeints002.isotach.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Given the improvements in 8.3 listed in the release notes:
- Improve efficiency of LIKE/ILIKE, especially for multi-byte character sets like UTF-8 (Andrew, Itagaki Takahiro)

Does this still hold:
http://www.postgresql.org/docs/8.3/interactive/locale.html

"The drawback of using locales other than C or POSIX in PostgreSQL is its performance impact. It slows character handling and prevents ordinary indexes from being used by LIKE. For this reason use locales only if you actually need them."

i.e. Do I still have to either initdb --locale=C or explicitly use text_pattern_ops?

(Queries include predicates of the form [indexed text expression] like "ABC%")

Stephen Denne

Disclaimer:
At the Datamail Group we value team commitment, respect, achievement, customer focus, and courage. This email with any attachments is confidential and may be subject to legal privilege. If it is not intended for you please advise by reply immediately, destroy it and do not copy, disclose or use it in any way.

__________________________________________________________________
This email has been scanned by the DMZGlobal Business Quality
Electronic Messaging Suite.
Please see http://www.dmzglobal.com/services/bqem.htm for details.
__________________________________________________________________

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-02-13 03:47:10 Re: REL8_3_STABLE branch created ...
Previous Message Bruce Momjian 2008-02-13 03:39:41 Branched for 8.4