Re: Database design for separate tsearch table

From: Mikkel Hgh <m(at)ooh(dot)dk>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Database design for separate tsearch table
Date: 2008-10-23 12:20:49
Message-ID: 20081023122049.GB16207@samson.jerusalem.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Oct 23, 2008 at 01:06:26AM +0200, Ivan Sergio Borgonovo wrote:
>weight them and you'll be able to search by field and "globally".
>
>I didn't make any scientific test but I previously had something
>like:
>
>create table subtable (
> subtableid int,
> body text,
> ftidx tsvector
>)
>create table maintable (
> maintableid int,
> body text,
> subtableid int
> ftidx tsvector
>);
>
>but it seem that just searching on a tsvector in maintable
>build up with
>
>setweight(to_tsvector('pg_catalog.english',
>coalesce(maintable.body,'')), 'A') || ' ' ||
>
>setweight(to_tsvector('pg_catalog.english',
>coalesce(subtable.body,'')), 'B')
>
>is faster.

Ok, that seems to be a good approach, thank you.

>Beware of the difference between gist and gin indexes for
>"restricted" weighted searches since with the latter you've to use
>@@@
Um, could you clarify that? I know the general differences between gist
and gin, but not how it affects weighted searches...

Kind regards,
Mikkel Hgh

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sergey Konoplev 2008-10-23 12:29:21 Re: Explain's estimation differs from real count enormously
Previous Message Sergey Konoplev 2008-10-23 12:02:21 Re: Explain's estimation differs from real count enormously