vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| > Actually, I think I figured it out. Please look over the GIST/GIN parts > of this patch and see if they're OK with you. Looks good, thank you. Why don't use suggested way for GIN index over tsvector? http://archives.postgresql.org/pgsql...4/msg00812.php It's nothing to cost light optimization... > This is still WIP because I haven't touched any contrib code, but > as far as the main backend goes I think it's ready to apply. Patch to all contrib modules: http://www.sigaev.ru/misc/contrib.patch.gz -- Teodor Sigaev E-mail: teodor@sigaev.ru WWW: http://www.sigaev.ru/ -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches |
| ||||
| Teodor Sigaev <teodor@sigaev.ru> writes: > Why don't use suggested way for GIN index over tsvector? > http://archives.postgresql.org/pgsql...4/msg00812.php I had forgotten the details :-(. Will adopt that code. >> This is still WIP because I haven't touched any contrib code, but >> as far as the main backend goes I think it's ready to apply. > Patch to all contrib modules: > http://www.sigaev.ru/misc/contrib.patch.gz Ooops, we duplicated work :-(. Will compare with your version before applying. regards, tom lane -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches |
| Thread Tools | |
| Display Modes | |
| |