[setr]

honestly I dont want plan hinting so much as being able to ban table-scanning / nested loops / etc on specific tables, and be able to set that independent of actual table-size so I can coerce its failure in dev environments

[silon42]

+1 I agree... (except nested loops are rarely the problem, they are often the best/simplest alternative for join).