Why I added CPU instead of another index for a 2.68-second spatial p95
A small production read-only load test and EXPLAIN analysis that separated a CPU-bound spatial path from two unrelated missing user-query indexes.
Data
Data pipelines, spatial queries, databases, measurement, and performance validation.
↗
Why I store coordinates as geometry but calculate meter searches as geography
A PostGIS design using expression-identical GiST indexes to preserve Hibernate and bounds-query compatibility without sacrificing correct radius and kNN semantics.
Making a 50,000-record spatial import safe to rerun
Natural keys, incremental persistence, and real HTTP contract tests for geocoding a coordinate-free public CSV into PostGIS.
When an expiry predicate dominates a PostGIS spatial query
How execution plans over 300,000 synthetic places and 210,000 reports showed that expiry aggregation—not the spatial GiST index—was the bottleneck.