Historically, @PostgreSQL resisted planner hints. Commercial forks and competitors sprout them, due to popular demand. In some sense, they are an admission of failure of the SQL project, and a step back to CODASYL DML. Know of a better plan? Then help us teach the planner!
-
-
We've been pragmatic in this area before, c.f. hacks around keeping OFFSET 0 a barrier, even when other OFFSET cases get optimized. Explicit CTE barrierness has less downsides than the OFFSET 0 business.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.