News for hackers. Stuff that matters.
Re:Working around a case where the Postgres planner is “not ... by protomyth on Monday August 02, 2021 @04:07PM (#28041938)
The worst part is database performance goes from great to sucky with no in between. Once a query's plan make it fall off a cliff, you really need the hints (forced indexes) that SQL Server provides to get the plan back to acceptable. Even updating the statistics tends not to fix the problem.

There are no comments on this comment yet.