"Tom Lane" <tgl@sss.pgh.pa.us> writes:
> This is in the regression database after a completed regression run, so
> it's possible that it's a bit different state from what's seen at the
> instant the cluster test was running, but it sure looks like the
> "expected" results are what you get from a seqscan. Would you force a
> seqscan and see what EXPLAIN shows as the cost on your machine?
Perhaps this comes down to 64 vs 32 bit datum and aligments and therefore
different size tables which because the planner does the lseek to measure the
table size shows up as different estimates for sequential scan costs?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com