On Wed, 14 Jan 2004, CoL wrote:
[plan1]
> -> Seq Scan on menutable b (cost=0.00..13.01 rows=38 width=22)
> (actual time=0.02..0.38 rows=38 loops=1)
[plan2]
> -> Index Scan using menutable_pkey on menutable b
> (cost=0.00..29.36 rows=38 width=22) (actual time=0.02..0.12 rows=38 loops=1)
It's estimating a cost of 13 for the sequence scan and 29 for the index
scan so it's choosing the sequence scan.
The value of random_page_cost may be too high for your system and
especially so if the database is small and likely to fit in ram. In
addition, if the table in question is small, you'll likely find that at
some point for a larger data set that the system switches over to an index
scan.
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
