Re: cannot get stable function to use index - Mailing list pgsql-general

From Tom Lane
Subject Re: cannot get stable function to use index
Date
Msg-id 13146.1451491790@sss.pgh.pa.us
Whole thread Raw
In response to Re: cannot get stable function to use index  (Andy Colson <andy@squeakycode.net>)
Responses Re: cannot get stable function to use index  (Andy Colson <andy@squeakycode.net>)
List pgsql-general
Andy Colson <andy@squeakycode.net> writes:
>     ->  Bitmap Index Scan on search_key  (cost=0.00..6.00 rows=1 width=0) (actual time=0.025..0.025 rows=0 loops=1)
>           Index Cond: (search_vec @@ to_tsquery('213 & E & 13 & ST & N'::text))

Hmm ... so the partial case actually is significantly more expensive than
the non-partial case: 4 msec vs .025 msec.  Still, that's about a 200x
penalty, not the 10000x penalty the planner is ascribing to it.

Thanks for the data!  I'll go moan about this on -hackers.

            regards, tom lane


pgsql-general by date:

Previous
From: Andy Colson
Date:
Subject: Re: cannot get stable function to use index
Next
From: Andy Colson
Date:
Subject: Re: cannot get stable function to use index