"Jim C. Nasby" <jim@xxxxxxxxx> writes: > One of the big problems with doing set enable_...=off is that there's no > way to embed that into something like a view, so you're almost forced > into putting into the application code itself, which makes matters even > worse. If you could hint this within a query (maybe even on a per-table > level), you could at least encapsulate that into a view. You've almost reinvented one of the points that was made in the last go-round on the subject of hints, which is that keeping them out of the application code is an important factor in making them manageable by a DBA. Hints stored in a system catalog (and probably having the form of "make this statistical assumption" rather than specifically "use that plan") would avoid many of the negatives. regards, tom lane
