Re: Multicolumn index including tsvector.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kris Gale <krisgale(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Multicolumn index including tsvector.
Date: 2009-11-24 00:12:35
Message-ID: 28097.1259021555@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Kris Gale <krisgale(at)gmail(dot)com> writes:
> So what I'm expecting here is that it'll be able to use one of those
> composite indexes to satisfy both the user_id and the vectors constraints.
> That doesn't seem to be the case, based on this query plan:

> explain analyze select body from example where user_id=1 and vectors @@
> to_tsquery('simple', 'when') limit 10;

Try coercing the '1' to a bigint. I don't believe the btree_gist
opclasses have any support for cross-type operators.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kris Gale 2009-11-24 00:15:40 Re: Multicolumn index including tsvector.
Previous Message Kris Gale 2009-11-23 23:08:17 Multicolumn index including tsvector.