avoid recasting text to tsvector when calculating selectivity - Mailing list pgsql-hackers

From Jan Urbański
Subject avoid recasting text to tsvector when calculating selectivity
Date
Msg-id 487E6097.2040707@students.mimuw.edu.pl
Whole thread Raw
Responses Re: avoid recasting text to tsvector when calculating selectivity  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I'm about to write a oprrest function for the @@ operator. Currently @@ 
handles multiple cases, like tsvector @@ tsquery, text @@ tsquery, 
tsquery @@ tsvector etc. The text @@ text case is for instance handled 
by calling to_tsvector and plainto_tsquery on the input arguments.

For a @@ restriction function, I need to have a tsquery and a tsvector, 
so in the text @@ text situation I'd end up calling plainto_tsquery 
during planning, which would consequently get called again during 
execution. Also, I'd need a not-so-elegant if-elsif-elsif sequence at 
the beginning of the function. Is this OK/unavoidable/easly avoided?

Cheers,
Jan
-- 
Jan Urbanski
GPG key ID: E583D7D2

ouden estin


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: Postgres-R: current state of development
Next
From: Oleg Bartunov
Date:
Subject: Re: [GENERAL] Fragments in tsearch2 headline