[GENERAL] Will be Wildspeed inside Postgresql contrib?

you have in mind, but it could be interesting if Postgresql could include this functionallity by default as well so, is there any plan to include Wildspeed on Postgresql contrib section? Thank you in advance. Regards, -- Mario Barcala http://www.mario.barcala.name -- Sent via pgsql-general ma

Re: [GENERAL] Will be Wildspeed inside Postgresql contrib?

And have both the same performance about searching speed? Is there any comparative and/or analysis? Thank you, Pavel Stehule wrote: [...] > >Same functionality has pg_trgm contrib module > -- Mario Barcala http://www.mario.barcala.name -- Sent via pgsql-general mailing li

[GENERAL] multi-word expression full-text searching

27;despite this'); to search the documents in which occur the expression "despite this". This last query gives the following error: ERROR: syntax error in tsquery: "despite this" Is it really impossible to searh a multi-word expression? Thanks in advance, Mario Barc

[GENERAL] NEAR operator

hives. Thanks, Mario Barcala -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

[GENERAL] How to remove the possibility to search the parts of a compound word with hyphen

write a new parser or are there any configuration issues to do this? Thanks, Mario Barcala -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Full text index without accents

ing value. I am a PL/SQL novice and I didn't find how to do it yet. Of course, then I will have to change upper experiment to my objective: to index without accents. I don't know if PL/SQL is the better option to build such function. Thanks, Mario Barcala > You can preprocess t

Re: [GENERAL] Full text index without accents

ERE to_tsvector('spanish',nonsensible(text)) @@ to_tsquery('spanish',nonsensible('word_with_accent')); respectively. I think postgreSQL uses both indexes as necessary. I believe to remember reading something about it in the documentation. Thank you very much, Mario

[GENERAL] Case sensitive full text searching

e the full text index: CREATE INDEX textindexsensible ON documento USING gin(to_tsvector('myconfiguration',texto)); But default behaviour of Simple Dictionary returns the lower-cased form of the word if it isn't in stopwords list. Is there any way to change this behaviour? Thanks