Re:Working around a case where the Postgres planner is “not ...
by icsa on Monday August 02, 2021 @05:48PM
(#28043123)
I had a similar situation a few years back. Postgres has constructs that are optimization barriers. Once I understood this and reviewed the Postgres source code to determine the semantics of the relevant constructs, it was possible to get a 10X improvement for complex set of queries that had already been optimized for several years.
[ Parent
| on HN ]
There are no comments on this comment yet.