... to avoid the LIKE operator where INSTR is sufficient
Some databases do even better: in postgres there is the option to index on regular expressions (or any string)
via the pg_trgm contrib extension.
Its disadvantage is huge index size but the gain can be enormous, as indeed in this, the OP's example:
-- table t is 112 MB, 1 million rows. The index is 190 MB (!)
-- all queries measured on second run (to avoid uninteresting cold cac
+he slowness)
-- no index:
SELECT * FROM t WHERE name like '%Franklin%' and name like '%Linsey%';
Time: 118.004 ms
SELECT * FROM t WHERE position('Franklin' in name)>0 AND position('Lin
+sey' in name)>0;
Time: 444.716 ms
create index t_trgm_re_idx on t using gin (name gin_trgm_ops);
-- with index:
SELECT * FROM t WHERE name like '%Franklin%' and name like '%Linsey%'
+ ;
Time: 1.582 ms
-- postgres specific regex-search syntax with '~'
SELECT * FROM t WHERE name ~ 'Franklin' and name ~ 'Linsey';
Time: 1.895 ms
The latter syntax has the added advantage that one can use regex like 'Frankl[iy]n' (it will use the trgm index as well).
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|