[yifanxuaaa]

inode_value and binding_hint now store many entries per row: append-only ≤4,000 B blocks, stored PLAIN with a CRC32C, the same block format on SQLite and PostgreSQL. This is schema v2. On fs-storage-quick, Q1 is −5.5% (SQLite) / −13.7% (PostgreSQL) and Q6 is −3.1% / −8.4%. D10 (diagnostic) goes from 52.9 to 49.8 MB on SQLite and from 70.4 to 61.0 MB on PostgreSQL.

Gap stage 1: fixes Ephemeral-AI-Lab/layerfs-project#91 (parent Ephemeral-AI-Lab/layerfs-project#84). Base: layerfs_v2_0_0 @ 8b701f42f0. It must merge together with the stacked #90 PR (schema v2 on PostgreSQL). Merging #91 alone would force #90 to a v3.

Commits

• b973426ee0 Blocks:
  • inode-value blocks with implicit ordinals, a per-block mode table, varint/zig-zag fields, and an exact 73-byte canonical round trip, so no object id changes;
  • binding-hint blocks;
  • schema v2 on both backends (v1 is refused);
  • tools/store_blocks.py for the optional offline SQLite migration and DIAGNOSTIC attribution.
  • LOC 139405 → 139919 (+514).
• 54486095d6 File digests: file_digest is kept only for chunked files. Small files are whole-file objects found by id at wave admission. +38.
• 017507ccf2 Save value memo: now keyed on the whole 73-byte value. This fixes a pre-existing bug: values differing only in mtime low bytes or nanoseconds got duplicate ordinals in one Save (D10: 953 extra rows). It wasted space but never returned wrong values. +3.

Codec frozen: field packing only. There is no zstd, LZ, dictionary or TOAST compression on these rows, and bodies are STORAGE PLAIN.

Measured and not done:

• Cross-Save ordinal reuse: needs a value index costing about what it saves.
• Small-pack coalescing: at most 0.8%, and needs a pack-grammar change.

Multi-writer contract (#84 gap design R1–R9)

Rule	How it holds
R1	Blocks are written inside the publication statement, so they commit with their packs (postgresql/objects/publish.rs:46–79). Hints are append-only.
R2	One statement per inode_values call (metadata/reads.rs:100–122); one json_each statement on SQLite.
R3	Location path unchanged.
R4	Lost-race and Collision unchanged. An overlapping block returns NULL, which becomes Integrity.
R5	Blocks are encoded before the lane (publish.rs:117); still one statement.
R6	INSERT … WHERE NOT EXISTS only, never UPDATE. Hint seq+1 under the lane.
R7	No compaction.
R8	Ordinals and groups never enter hashed ids.
R9	Same statement count; hint writes use fewer statements.

Tests

222 test executables pass on the stacked head (persistence incl. PostgreSQL, storage, daemon, store-service, workspace, project). clippy -D warnings, fmt, the boundary guard and tools/test_store_blocks.py all pass.

fs-storage-quick (qgap-c2b, against the Phase 2 baseline 02133596ae; 12/12 PASS, no regressions)

Case	SQLite net	PostgreSQL net
Q1	4,796,416 → 4,534,272 (−5.5%)	6,119,424 → 5,283,840 (−13.7%)
Q3	same	942,080 → 753,664 (−20.0%)
Q4	same	1,343,488 → 1,155,072 (−14.0%)
Q6	24,399,872 → 23,650,304 (−3.1%)	28,999,680 → 26,550,272 (−8.4%)

On D10 PostgreSQL, inode_value goes 9.39 → 2.84 MB and binding_hint 3.26 → 0.43 MB.

Speed gate (fs-bench-quick, Docker, interleaved control/candidate/candidate/control, quiet host)

• g91, both backends, 144/144 rows: one REGRESSION, on C09 PostgreSQL Exec (cat of the committed 64 MiB file): 102.9/103.3 → 116.0/120.1 ms, ratio 1.12.
• Investigation: that phase runs the same 6 PostgreSQL statements in every sample, and none reads inode values, so there are 0 block decodes. No v0.1.4 phase 2: benchmark against v0.1.3 and repair severe regressions #91 code runs there. A diagnostic 50-samples-per-build A/B showed no difference. End-to-end ratio 1.00.
• g90 (stacked v0.1.4 phase 2: benchmark against v0.1.3 and repair severe regressions #91 + Storage adoption phase 1: resolve correctness, compatibility and integration blockers #90, PostgreSQL): C09 PostgreSQL Exec ratio 0.85. Every other gating ratio in g91 was ≤1.058.
• PostgreSQL Commit buffers hit: −57% (C01), −85% (C04), −58% (C16). Locate round trips unchanged.
• Owner decision needed: the gate rule flags a regression in each run (C09 in g91, C14 in g90). Both are on Exec phases that this change does not touch. The recorded gate verdicts are kept and not re-sampled.

Migration

• SQLite v1 Stores: refused at open with Refused, naming tools/store_blocks.py migrate. The migration is optional and offline: it writes a checked v2 copy from a closed v1 copy.
• PostgreSQL v1 schemas: refused, with no conversion tool. Ship it for new Stores.

🤖 Generated with Claude Code