Hi!
I eventually tried with an 'vacuum analyse' which made postgres to use my index
and the query was completed in 200 ms (insted of tens of seconds) and I was
happy again!
Thanks!
/Rickard
Citerar Tom Lane <[EMAIL PROTECTED]>:
> Rickard =?iso-8859-1?b?U2r2c3Ry9m0=?=
> <[EMAIL PROTECTED]> writes:
> > fast db:
> > -------------------------
> > -> Index Scan using testcase_b_bid_index on testcase
> (cost=0.00..1656.82 rows=426 width=38) (never executed)"
> > -------------------------
>
> > slow db:
> > -------------------------
> > -> Seq Scan on testcase (cost=0.00..2896.42 rows=33242
> width=64) (actual time=77.027..791.014 rows=37093 loops=1)"
> > -------------------------
>
> Let's see the query and the *whole* explain analyze output, not the
> part
> you (mistakenly) think is important.
>
> regards, tom lane
>
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
