<br /><div class="gmail_quote">2010/3/29 Tom Lane <span dir="ltr"><<a
href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>></span><br/><blockquote class="gmail_quote" style="margin: 0pt
0pt0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">Łukasz Dejneka <<a
href="mailto:l.dejneka@gmail.com">l.dejneka@gmail.com</a>>writes:<br /> > What I want to do is to use HStore data
type(namely the HStore keys) in<br /> > TSearch. I don't want use TSVector and the original ts_match_vq function,<br
/>> because I want to be able to control exact values that are passed to the<br /> > search and not use their
lexemes.<br/><br /></div>If that's what you're after, why don't you set up a text search<br /> configuration in which
theparser/dictionary are trivial and do no<br /> transformations of the strings (beyond perhaps splitting at
whitespace)?<br/> Seems a lot easier than constructing your own datatype and all the<br /> required support
functions.<br/><br /> regards, tom lane<br /></blockquote></div><br />Hi,<br /><br />Thanks for
theidea, but unfortunately it's not an option for me... This needs to be expendable in the near future, so need to be a
codedas a separate function :/<br />