DevelopmentPlanet PostgreSQL
Development
Incremental sort exploits presorted data to avoid expensive full sorts, but cost estimation errors on skewed data can backfire.
Everyone knows not to store money as a double precision. One can hope. The rule is so well drilled that it has stopped being interesting, and it is also not where the trouble usually starts. The float is already in the schema before anyone…
Step one in the quest for good transit in Kingston: hexagons, census data, and a whole lot of ST_Intersection.
Diagnose spilling hash joins with `enable_hashjoin = off`.