On 8/18/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> Trevor Talbot wrote:
> > Well, you could create a function that returns a tsvector, but how do
> > you get that to work with queries? I've been under the impression the
> > expressions need to match (in the normal case, be the same function
> > with the same arguments) in order to use the index.
>
> Yes, so you create a function called complex_ts and create the index:
>
> CREATE INDEX ii on x USING GIT(complex_ts(col1, col2))
>
> and in your WHERE clause you do:
>
> WHERE 'a & b' @@ complex_ts(col1, col2)
Oh, duh, of course. I kept thinking of the index as something
abstract instead of reusing the expression, even when the examples
were right in front of me...
On 8/18/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> Bruce Momjian wrote:
> > CREATE INDEX ii on x USING GIT(complex_ts(col1, col2))
>
> GIN?
Freudian slip, that's what he thinks of me :D
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
