Re: WIP: index support for regexp search
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Erikjan Rijkers <er@xs4all.nl>, Heikki Linnakangas <hlinnakangas@vmware.com>, Tomas Vondra <tv@fuzzy.cz>, pgsql-hackers <pgsql-hackers@postgresql.org>, Pavel Stìhule <pavel.stehule@gmail.com>
Date: 2013-04-08T05:28:39Z
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 →
-
Fix filling of postmaster.pid in bootstrap/standalone mode.
- c29947722955 9.3.0 cited
-
Add explicit casts in ilist.h's inline functions.
- e78d288c895b 9.3.0 cited
Attachments
- trgm-regexp-0.16.patch.gz (application/octet-stream) patch
Alexander Korotkov <aekorotkov@gmail.com> writes: > [ trgm-regexp-0.15.patch.gz ] I spent the weekend hacking on this, making a number of bug fixes and a whole lot of cosmetic changes. I think there are large parts of this that are in committable shape now, but I still find the actual graph transformation logic to be mostly unintelligible. I think what's most obscure is the distinction between the arcs list and the keys list of each state in the expanded graph. I get the impression that the general idea is for the arcs to represent exactly-known transitions while the keys represent imprecisely-known transitions ... but there seems to be at least some leakage between those categories. Could you write down a specification for what's supposed to be happening there? regards, tom lane