Re,
With modifing parameters like this :
ALTER TABLE keywords ALTER keyword SET STATISTICS 100;
ALTER TABLE keywords ALTER k_id SET STATISTICS 100;
ALTER TABLE engine ALTER k_id SET STATISTICS 100;
ALTER TABLE engine ALTER f_id SET STATISTICS 100;
vacuuming both tables
and rewriting the queries
Hello,
Tom Lane a écrit :
Antoine Bajolet <[EMAIL PROTECTED]> writes:
We are using postgresql in a search engine on an intranet handling
throusand of documents.
But we ave a big problem when users use more than two search key.
I think you need to increase the statistics targets for
Antoine Bajolet <[EMAIL PROTECTED]> writes:
> We are using postgresql in a search engine on an intranet handling
> throusand of documents.
> But we ave a big problem when users use more than two search key.
I think you need to increase the statistics targets for your keywords
table --- the estima
On Sat, 2005-09-17 at 17:47 +0200, Antoine Bajolet wrote:
> There are more tables around, but the heart of the search engine is
> made of three tables :
>
> fiches (f_id int4, f_title varchar) 52445 rows
> engine (f_id int4, k_id int4, weight )11761700 rows
> keywords(k_id, keyword