From: | Rod Taylor <pg(at)rbt(dot)ca> |
---|---|
To: | Bob Arens <martian(dot)bob(at)gmail(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Query plan discrepancies |
Date: | 2004-07-17 02:28:18 |
Message-ID: | 1090031298.81714.8.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Have you run ANALYZE recently?
Please send back EXPLAIN ANALYZE for the below query.
> EXPLAIN from DB 2 (doesn't come back):
> QUERY PLAN
> -------------------------------------------------------------------------------------------------------------------------
> HashAggregate (cost=7763.55..7763.56 rows=1 width=8)
> -> Nested Loop (cost=4363.86..7763.55 rows=1 width=8)
> -> HashAggregate (cost=4363.86..4363.86 rows=200 width=146)
> -> Seq Scan on word_stats_base (cost=0.00..4126.09
> rows=95109 width=146)
> -> Index Scan using medline_abstract_tokens_norm on
> medline_abstract_tokens (cost=0.00..16.99 rows=1 width=8)
> Index Cond: ((medline_abstract_tokens.norm)::text =
> ("outer".norm_token)::text)
> Filter: (pmid = 7968456)
> (7 rows)
From | Date | Subject | |
---|---|---|---|
Next Message | Gaetano Mendola | 2004-07-17 09:49:08 | Re: FOR-IN-EXECUTE, why fail? |
Previous Message | Peter Eisentraut | 2004-07-16 20:48:43 | Re: BYTEA output presentation |