Re: Workaround: Planner preference for tsquery filter vs. GIN index in fast text search

From: Oleg Bartunov <obartunov(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Laurence Parry <greenreaper(at)hotmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Workaround: Planner preference for tsquery filter vs. GIN index in fast text search
Date: 2014-04-22 07:15:02
Message-ID: CAF4Au4zrP8r3=Up3ySxTfZwQcLEpn=h60D6OknP3k=68y25x4g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Apr 22, 2014 at 10:28 AM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> On 04/20/2014 07:46 AM, Oleg Bartunov wrote:
>>
>> btw, 9.4 should be wiser in case of rare+common terms, thanks to GIN
>> fast scan feature.
>
>
> Indeed, although we didn't actually do anything to the planner to make it
> understand when fast scan helps. Doing something about cost estimation is
> still on the 9.4 Open Items list, but I don't have any ideas on what to do
> about it, and I haven't heard anything from Alexander about that either.
> That means that the cost estimation issue Laurence saw is going to be even
> worse in 9.4, because GIN is going to be faster than a seq scan in more
> cases than before and the planner doesn't know about it.
>
> - Heikki

You are right, we should return to that topic.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Ivan Voras 2014-04-22 07:57:14 Re: tsearch2, large data and indexes
Previous Message Heikki Linnakangas 2014-04-22 06:40:37 Re: tsearch2, large data and indexes