the migration-lock census reads the two scratch-database sites tests/proposal_read.rs adds, Scratch::new and restore_the_views, both of which already hold pg::migration_serial's cluster lock, so the unlocked list stayed empty and only the set it reads before trusting moved: ci/local.sh caught it red on the census and green once named. with the carried line, ci/local.sh is green against Postgres 18 (4229 passed over 135 binaries, 9 ignored), proposal_read's four among them run against the cluster rather than skipped; one earlier run lost loot-core's concurrent_stage_of_same_address_does_not_tear to an os error 5 on a rename, which passed three times alone and is filed as a sighting (#2175) aa12f574 · 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.