John Major wrote: > ~there are indexes on all of the fields being joined (but not on > library_id or clip_type ). ~Everything has been re-analyzed post index > creation > ~I've tried "set enable_seqscan=off" and set (join_table_order or > something) = 1 Seqscanning and sorting a table is generally faster than a full scan of the table using an index scan, unless the heap is roughly in the index order. You probably need to CLUSTER the tables to use the indexes effectively. Are you sure you have an index on sequence_alignment.sequence_id? The planner seems to choose a seqscan + sort, even though you've set enable_seqscan=false. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
