| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | jesper(at)krogh(dot)cc, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Queryplan within FTS/GIN index -search. |
| Date: | 2009-10-23 19:22:03 |
| Message-ID: | 1256325723.28858.60.camel@monkey-cat.sm.truviso.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, 2009-10-23 at 17:27 +0100, Richard Huxton wrote:
> Returns an array of keys given a value to be queried; that is, query is
> the value on the right-hand side of an indexable operator whose
> left-hand side is the indexed column
>
> So - that is presumably two separate arrays of keys being matched
> against, and the AND means if the first fails it'll never check the second.
My point was that if it's only one index scan in both cases, then GIN
should have the same information in both cases, right? So why are they
being treated differently?
I must be missing something.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jesper Krogh | 2009-10-23 19:29:45 | Re: Calculating selectivity for the query-planner on ts_vector colums. |
| Previous Message | Tom Lane | 2009-10-23 19:11:15 | Re: Calculating selectivity for the query-planner on ts_vector colums. |