[hans_castorp]

> Any query that's not a one-off should not perform any table scans. A table scan today can mean an outage tomorrow

I disagree.

There are queries where a table scan is the most efficient access strategy. These are typically analytical/aggregation queries that usually query the whole table. And sometimes getting only 50% of all rows is better done using a table scan as well.

I also don't see how a (read only) "table scan" could leave to an outage. It won't block concurrent access. The only drawback is that it results in a higher I/O load - but if the server can't handle that, it would assume it's massively undersized.

[magicalhippo]

I mentioned in a different reply that I did not have analytic queries in mind. I don't work with that so forgot to specify.

Outage might "just" mean slow enough that customer can't get their work done in time. For the customer it's the same.