| From: | Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
|---|---|
| To: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Mnogosearch (Was: Re: website doc search is ... ) |
| Date: | 2004-01-01 08:05:05 |
| Message-ID: | 3FF3D4B1.2010607@paradise.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Might be worth trying a larger statistics target (say 100), in the hope
that the planner then has better information to work with.
best wishes
Mark
Marc G. Fournier wrote:
>
>he problem is that right now, we look at the LIKE first, giving us ~300k
>rows, and then search through those for those who have the word matching
>... is there some way of reducing the priority of the LIKE part of the
>query, as far as the planner is concerned, so that it will "resolve" the =
>first, and then work the LIKE on the resultant set, instead of the other
>way around? So that the query is only checking 15k records for the 13k
>that match, instead of searching through 300k?
>
>I'm guessing that the reason that the LIKE is taking precidence(sp?) is
>because the URL table has less rows in it then ndict8?
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dinesh Pandey | 2004-01-01 09:43:48 | Re: [SQL] index row size 2728 exceeds btree maximum, 2713 |
| Previous Message | Dustin Sallings | 2004-01-01 06:52:43 | Re: speeding up inserts |