> I was told that DB2 has per-table (or rather per-tablespace) knowledge > of disk speeds, so keeping separate random and seqsqan costs for each > table and index could be a good way here (to force use of a particular > index make its use cheap) >
I was wondering something even easier, keeping 1 cost per index, 1 cost per seqscan, but being allowed to scale cost for each index on each query(recommended, null or unrecommended) Regards ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
