Re: [HACKERS] avoid recasting text to tsvector when calculating selectivity

Jan Urbański wrote: Tom Lane wrote: =?UTF-8?B?SmFuIFVyYmHFhHNraQ==?= <[EMAIL PROTECTED]> writes: 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 inst

Re: [HACKERS] avoid recasting text to tsvector when calculating selectivity

Tom Lane wrote: =?UTF-8?B?SmFuIFVyYmHFhHNraQ==?= <[EMAIL PROTECTED]> writes: 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 call

Re: [HACKERS] avoid recasting text to tsvector when calculating selectivity

=?UTF-8?B?SmFuIFVyYmHFhHNraQ==?= <[EMAIL PROTECTED]> writes: > 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_tsv

[HACKERS] avoid recasting text to tsvector when calculating selectivity

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 @@ restrict