Re:Working around a case where the Postgres planner is “not ...
by rrrrrrrrrrrryan on Monday August 02, 2021 @05:17PM
(#28042783)
Is it possible to at least lock-in a query plan with Postgres?
I understand the philosophy behind wanting to keep the queries themselves as declarative as possible, but there should be some way to prevent a really important query from randomly going rogue and using a stupid index, just because something completely unrelated changed somewhere else in the database.
I understand the philosophy behind wanting to keep the queries themselves as declarative as possible, but there should be some way to prevent a really important query from randomly going rogue and using a stupid index, just because something completely unrelated changed somewhere else in the database.