ADR 0075 re-decides the proposal ingest fallback across history sizes on a throwaway Postgres 18: a push with ten proposals open grows from about 5 ms at 1,000 changes to about 520 ms at 300,000 while a push with none open stays flat at 2 to 3 ms, and the growth is the repo graph read, which past a planner step, between about 1,450 and 1,550 changes on a forge of about 288,000 edges, scans the whole global change_parent table and so follows the forge edge count as well as the repo history (55 to 123 ms at 30,000 changes as the forge grew to about 893,000 edges). the knowingly-wrong arm, a graph read per proposal, read about ten times the ten-open arm at each size from 3,000 up. the fallback is retired: offer, fetch and propose read make the same read, and since #2175 the web reads state from the column the fallback would leave open. the no-proposal cost, 0.11 to 0.48 ms and flat in history, is recorded and not closed, since skipping the read needs a new column or a cache. store.rs notes the plan step at repo_change_graph. docs only: no code, no migration, no deploy owed. the workspace suite is green (4400 passed over 139 binaries, 13 ignored) (#2312) 223b87d4 · dbf3dbe6…
Renames are not followed. loot's tree maps a path to an address, so a rename is a delete and an add. This list is the history of the name, not of the bytes.