Re: WIP: index support for regexp search

Alexander Korotkov <aekorotkov@gmail.com>

From: Alexander Korotkov <aekorotkov@gmail.com>
To: Erik Rijkers <er@xs4all.nl>
Cc: Heikki Linnakangas <hlinnakangas@vmware.com>, Tom Lane <tgl@sss.pgh.pa.us>, Tomas Vondra <tv@fuzzy.cz>, pgsql-hackers@postgresql.org, pavel.stehule@gmail.com
Date: 2012-12-18T08:45:27Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix filling of postmaster.pid in bootstrap/standalone mode.

  2. Add explicit casts in ilist.h's inline functions.

On Tue, Dec 18, 2012 at 11:45 AM, Erik Rijkers <er@xs4all.nl> wrote:

> On Tue, December 18, 2012 08:04, Alexander Korotkov wrote:
> I ran the same test again: HEAD versus trgm_regex v6, 7 and 9.  In v9
> there is some gain but also
> some regression.
>
> It remains a difficult problem...
>
> If I get some time in the holidays I'll try to diversify the test program;
> it is now too simple.
>

Note, that regexes which contains {,n} are likely not what do you expect.

test=# select 'xq' ~ 'x[aeiou]{,2}q';
 ?column?
----------
 f
(1 row)

test=# select 'xa{,2}q' ~ 'x[aeiou]{,2}q';
 ?column?
----------
 t
(1 row)

You should use {0,n} to express from 0 to n occurences.

------
With best regards,
Alexander Korotkov.