Graham McIntire
c7e7472c57
Weather.find_nearest_hrrr/3 and Weather.find_nearest_native_profile/3 run a three-range scan gated first by a ±1h valid_time window, then by a ±0.07° lat/lon box. The existing unique `(lat, lon, valid_time)` index is only usable on its `lat` prefix for these queries, forcing Postgres to scan wide lat slices before applying the valid_time filter — expensive on the Turing Pi 2 node. Add a `(valid_time, lat, lon)` composite so valid_time leads, collapsing the search to a narrow btree slice inside a single partition before the lat/lon box filter kicks in. `hrrr_profiles` is RANGE-partitioned by valid_time, so CREATE INDEX CONCURRENTLY is applied per partition and the resulting indexes are attached to a parent index created ON ONLY the partitioned table. `hrrr_native_profiles` is a regular table, so the concurrent build runs directly on it. |
||
|---|---|---|
| .. | ||
| migrations | ||
| import_contacts.exs | ||
| import_weather.exs | ||
| seeds.exs | ||