4 ms·
You've never run into a query planner that suddenly changes its mind once your tables grow. Try using row level security in postgres - it's awfully slow and yo
by mickeyp 3y ago
You've never run into a query planner that suddenly changes its mind once your tables grow.
Try using row level security in postgres - it's awfully slow and you need to be a master architect and sql developer to make it run fast because it's too dumb on its own. With query planner hints I could at least guide it. Shame pg doesn't believe in that.
- _a_a_a_ 3y agoPoster said oracle not PG
- mardifoufs 3y agoTotal db noob here: is Oracle's query planner better? What's the difference between the two?
- _a_a_a_ 3y agoThis is not about Oracle versus postgres, it's about whether or not to use hints. My position is that needing hints indicates a failure of the database optimiser. The optimiser theoretically should do a perfect job. In practice it doesn't, and never can so sometimes hints are necessary, but IME and speaking as an MSSQL guy, I very rarely need them.
- mickeyp 3y agoOracle has query hints; pg does not. Query planner hinters are useful. That's my point.