Files
buzz/migrations
hMB2 43c97fa84b db: start existing read accounts in 0057; correct deployment wording
Under 0056 only a read intent creates personal_read_accounts rows, so every
existing account has started. Leaving started_at NULL would hide everything
that arrives between deploy and the account's next intent. 0057 now sets
started_at to the migration's time for accounts in active communities; the
write fence would reject fenced or deleting ones. A migration test covers an
existing account (unread mention after upgrade, no new intent) next to a
fenced community's account.

Docs: bounded locking still lets ingestion queue within the budget, and a
non-prebuilt index on a large event_mentions times out and rolls back.

Signed-off-by: hMB2 <0400eb0da32afbbf16cdd1dee6ffd243587e8f3d6a2823fe7dfa95d16b002b7d@buzz.block.builderlab.xyz>
2026-10-07 12:11:10 -07:00
..