Re: Using HStore type in TSearch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Łukasz Dejneka <l(dot)dejneka(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Using HStore type in TSearch
Date: 2010-03-29 14:43:14
Message-ID: 12820.1269873794@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

=?ISO-8859-2?Q?=A3ukasz_Dejneka?= <l(dot)dejneka(at)gmail(dot)com> writes:
> What I want to do is to use HStore data type (namely the HStore keys) in
> TSearch. I don't want use TSVector and the original ts_match_vq function,
> because I want to be able to control exact values that are passed to the
> search and not use their lexemes.

If that's what you're after, why don't you set up a text search
configuration in which the parser/dictionary are trivial and do no
transformations of the strings (beyond perhaps splitting at whitespace)?
Seems a lot easier than constructing your own datatype and all the
required support functions.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joachim Wieland 2010-03-29 14:46:48 Parallel pg_dump for 9.1
Previous Message Alvaro Herrera 2010-03-29 14:42:19 Re: enable_joinremoval