> But I also asked for _ordered_ results, which the seq scan is not
> covering, but the index does... and I specifically disabled sequential
> scan.
Docs say:
> Enables or disables the query planner's use of sequential scan plan
> types. It's not possible to suppress sequential scans entirely, but
> turning this variable off discourages the planner from using one if
> there are other methods available.
Note the second sentence. Again, I think it will have to scan the
whole table anyway, because that's what you've asked for, and given
that, enable_seqscan=off doesn't apply.
- John Burger
MITRE
