Paul Trowbridge 748e301464 Steer /agg off the sort-based GroupAggregate plan ... pf_logid arrives pre-sorted off its index, so the planner picks an Incremental Sort GroupAggregate on the strength of that "free" sort — but comparing 30+ grouping columns per row makes it 5-7x slower in practice than a HashAggregate. Confirmed via EXPLAIN ANALYZE on fc_osm_skinny_34: 34-50s sorted vs ~7-10s hashed, independent of work_mem or stats (ANALYZE didn't change the plan choice). Scoped to this transaction only, since disabling incremental sort globally could hurt some other query's plan. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>		2026-09-22 22:32:24 -04:00
..
auth.js	Read territory at login, and survive having none	2026-09-18 11:52:00 -04:00
layouts.js	Make a pivot layout a thing people own and publish	2026-09-19 14:20:04 -04:00
log.js	Record what a write ran against, and the statement it ran	2026-09-18 12:19:40 -04:00
operations.js	Steer /agg off the sort-based GroupAggregate plan	2026-09-22 22:32:24 -04:00
plans.js	Drop Shift years	2026-09-21 12:39:07 -04:00
sources.js	Make a pivot layout a thing people own and publish	2026-09-19 14:20:04 -04:00
tables.js	Read source columns from pg_catalog, not information_schema	2026-09-18 16:12:05 -04:00
versions.js	Manage a version's tags as a list, not one entry at a time	2026-09-22 09:00:27 -04:00