pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mitch Vincent <mitch@venux.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: Full text indexing (and errors!)
Date: Sun, 21 May 2000 15:44:15 -0400
Message-ID: <10468.958938255@sss.pgh.pa.us> (raw)
In-Reply-To: <002f01bfc358$f82cfee0$0300000a@doot.org>
References: <00db01bfc345$e5400100$0300000a@doot.org>
	<9916.958931894@sss.pgh.pa.us>
	<001c01bfc350$d6d8ddc0$0300000a@doot.org>
	<10020.958933715@sss.pgh.pa.us>
	<002f01bfc358$f82cfee0$0300000a@doot.org>

"Mitch Vincent" <mitch@venux.net> writes:
>  attname | attdisbursion | starelid | staattnum | staop | stanullfrac |
> stacommonfrac | stacommonval | staloval | stahival
> ---------+---------------+----------+-----------+-------+-------------+-----
> ----------+--------------+----------+----------
>  string  |    0.00208943 |  1161760 |         1 |  1066 |           0 |
> 0.0100436 | on           | 00       | zzz

Hmm, so the most common word is "on" accounting for about 1% of the
entries.  Although I don't think that stacommonfrac directly affects
this particular query plan, it'd still be a good idea to try to push it
down.  fti.c has a provision for ignoring "stop words", but its stopword
list seems to be empty by default.  You might want to throw in "the" and
"on" and any other noisewords you're unlikely to want to search for.
That should help reduce the size of the fti table, too...

Actually ... waitasec.  stacommonfrac *does* affect this query plan in
7.0 release.  Before you do anything else, try enabling the new LIKE
estimator code (see contrib/likeplanning/ for details) and see what
sort of plan you get then.  The estimated selectivity should go *way*
down, and that ought to change the plan.

You'd still be well advised to get rid of as many stop words as you can.

			regards, tom lane



view thread (6+ messages)

Message-ID: <10468.958938255@sss.pgh.pa.us>
Permalink:  ../10468.958938255@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/10468.958938255@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, mitch@venux.net
  Subject: Re: Full text indexing (and errors!)
  In-Reply-To: <10468.958938255@sss.pgh.pa.us>
  References: <00db01bfc345$e5400100$0300000a@doot.org> <9916.958931894@sss.pgh.pa.us> <001c01bfc350$d6d8ddc0$0300000a@doot.org> <10020.958933715@sss.pgh.pa.us> <002f01bfc358$f82cfee0$0300000a@doot.org> <10468.958938255@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox