Skip to content

refactor(db): move maintenance store ownership - #6814

Closed
TheSentinel454 wants to merge 1 commit into
codex/issue-2-admin-moderation-storefrom
codex/issue-2-maintenance-store
Closed

refactor(db): move maintenance store ownership#6814
TheSentinel454 wants to merge 1 commit into
codex/issue-2-admin-moderation-storefrom
codex/issue-2-maintenance-store

Conversation

@TheSentinel454

@TheSentinel454 TheSentinel454 commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Current reconstructed head

Exact base: codex/issue-2-admin-moderation-store at 102fca801dfdb3bab867deb4fab615718d03c6fc
Exact head: codex/issue-2-maintenance-store at 3ea91d34db1b9feee9ae73a71622e86fe828ccdb

This current head removes crates/buzz-db/tests/store_ownership.rs; no replacement path-sensitive ownership test is introduced. Apart from removing that complete test-file diff, the production patch is byte-for-byte identical to the previously reviewed slice. This remains part of tracker #2 and the #17/#19 acceptance work.

Independent exact-head review from a separate clean Blox workstation found no issues. Current-head evidence passed formatting, strict buzz-db clippy, 111 non-PostgreSQL library tests with 200 PostgreSQL tests ignored, the observability source test, relay consumer compilation, exact ownership/unique-span review checks, and 3 focused partition validation unit tests (this slice moves no PostgreSQL test group) on native PostgreSQL where applicable.

Summary

Continue tracker #2 by moving the two remaining startup-maintenance Db facades to the modules that own their invariants: monthly partition creation to partition.rs, and NIP-33 d_tag materialization to event.rs.

The public Db API is unchanged. There is no dedicated domain issue for this tightly coupled maintenance slice; it completes two remaining ledger items while advancing #17 and #19.

Stack

  • Tracker: TheSentinel454/buzz#2
  • Domain issue: none; startup partition/event maintenance is tracker-led
  • Test ownership acceptance: #17
  • Span ownership acceptance: #19
  • Exact base: codex/issue-2-admin-moderation-store at 7dbb399 (#6813)
  • Exact head: codex/issue-2-maintenance-store at fcb55ab

Domain moved

  • Db::ensure_future_partitions and its existing datastore span to partition.rs, beside the partition allowlist, validation, DDL implementation, and focused tests
  • Db::backfill_d_tags, its unchanged event-table SQL, and its existing datastore span to event.rs

crates/buzz-db/src/lib.rs falls from 3,717 to 3,690 lines.

Non-goals

  • Startup ordering, scheduling, logging, or error handling in the relay
  • Partition ranges/allowlist/DDL, d_tag backfill SQL or event semantics, schema, locking, retries, timeouts, or client-visible behavior changes
  • Moving general event-insertion materialization helpers
  • Generic store traits, raw pool access, executor migration, or crate reorganization

Risk

Low semantic risk. Both public facades and their fixed-name spans moved intact; each continues to call or execute the same module-owned implementation using the same writer pool. No tests or production SQL changed.

Blox verification

Author workstation: buzz-tornquist-issue-2-store-stack (2046520), exact head 197549b3a28f2604d164208c4dd16e979458bb6c.

  • cargo fmt --all --check
  • git diff --check c684825860900357e017dd4102bc4df88dd6ec2e..HEAD
  • cargo clippy -p buzz-db --all-targets -- -D warnings
  • cargo clippy -p buzz-relay --all-targets -- -D warnings
  • cargo test -p buzz-db --lib: 108 passed, 200 ignored, including all three partition validation tests and event materialization unit coverage
  • cargo test -p buzz-db --test observability_source: 1 passed
  • cargo test -p buzz-relay --lib: 909 passed, 48 ignored
  • Commit hooks passed without bypass; the disposable workstation has no user signing key, so the commit itself is unsigned

Independent exact-head Blox review: pending.

Remaining tracker work

Next: deletion-store facades, the remaining cross-domain helper audit, and the final runtime-boundary/test assessment.

Superseded pre-comment restack verification

PR #6700 merged before publication completed. This layer was restacked onto current main through the exact parent named above; the final cumulative tip is 2ddcc8a. Cumulative author gates passed: formatting and diff checks; buzz-db and buzz-relay all-target clippy with -D warnings; DB lib 111 passed / 200 ignored; ownership 22/22; observability 1/1; the full isolated PostgreSQL domain matrix; and relay lib 910 passed / 49 ignored.

Result

No findings.

Exact revision and isolation

  • Base: bcb1b423b7ac029759777209505800a757adc53b
  • Head: 5c314af38a0707e5f932b6627ea688d1ac7c9d33
  • Verified head parent and merge-base: exact base above
  • Reviewer workstation: buzz-tornquist-pr-6814-final-review (2057668)

The fresh shallow workstation was clean and unclaimed, had no competing commands, and had no Buzz production relay credentials or ownership-report file.

Review conclusions

  • ensure_future_partitions moves to partition.rs; backfill_d_tags and its unchanged NIP-33 UPDATE move to event.rs.
  • Both public signatures, delegation/SQL, error behavior, fixed span names, and one-span ownership are preserved.
  • The guard proves the maintenance facades no longer remain in lib.rs. At this head, its only remaining datastore spans are the runtime read_session_query_events and migrate spans.

Verification

  • Diff check and Rust formatting: passed.
  • Buzz DB and relay all-target clippy with -D warnings: passed.
  • Buzz DB library: 111 passed, 200 ignored.
  • Native PostgreSQL 17.11, migrations complete: three partition validation tests passed.
  • An external exact-head facade probe invoked Db::ensure_future_partitions(0) and Db::backfill_d_tags() successfully against the migrated database (maintenance_backfilled=0).
  • Final detached head remained clean; no duplicate datastore-span names were found.

Artifacts: pr-6814-final-review-artifacts.tgz, SHA-256 f16c5917bd9b238b332f6f4ecc0db49169c6455ddf1652baab170b8bfa715875. Archive and internal checksums were verified locally.

Comment-addressed restack

Review follow-up on #6777 removed only the low-value replaceable ownership source test. This PR was restacked onto its rewritten parent; its production patch is unchanged.

  • Exact base: 7dbb399207515d12fc9b27036076e5d4f6bfb937
  • Exact head: fcb55abb9018f03c74bb4ec52b32422ad253e62f
  • Final cumulative tip: 6fa2f104d42c6ba85bdf62e7ccb74ceaf4a84f67
  • Per-layer patch-ID and tree audits confirm this PR’s production diff is unchanged from its pre-comment head.
  • Cumulative Blox gate: formatting and diff checks; strict buzz-db/buzz-relay Clippy; DB lib 111 passed / 200 ignored; ownership 21/21; observability 1/1; every moved PostgreSQL test; relay lib 910 passed / 49 ignored.
  • Independent re-review at this exact head: no findings; fresh exact-parent/head Blox review passed fmt/diff, strict buzz-db/buzz-relay Clippy, DB lib and current ownership/observability/unique-span guards, 3 maintenance PostgreSQL tests, relay compilation, and the exact-head facade probe.

Signed-off-by: OpenAI Codex <codex@openai.com>
@TheSentinel454

Copy link
Copy Markdown
Contributor Author

🤖 Superseded by #6987, which consolidates the remaining issue #2 store-extraction stack onto merged #6782. #6987 is an open draft at the independently reviewed exact head, and all exact-head CI checks are green. This PR remains available for review history; please continue review on #6987.

TheSentinel454 added a commit that referenced this pull request Aug 28, 2026
## Summary

Finish the remaining database-store extraction tracked by
[TheSentinel454#2](TheSentinel454#2)
in one reviewable PR.

This consolidates the previously stacked domain slices after #6782
merged. It preserves the runtime/store boundary established by #6660,
#6668, #6700, and #6782 while separating database runtime infrastructure
from domain-owned persistence:

- `runtime/` owns pool construction and sizing, writer/reader routing,
read sessions and route proofs, transaction infrastructure,
observability primitives, replica fencing, health support, migrations,
and cross-cutting runtime tests.
- `store/` owns domain records, SQL, row parsing, locks and invariants,
`Db` domain methods, focused tests, and logical-operation datastore
spans.
- `lib.rs` remains a 57-line compatibility facade that preserves
existing crate-root paths and `Db` method signatures through re-exports.

Domain coverage includes API tokens, authentication allowlists,
reminders, event queries, threads, reactions, feeds, users and DMs,
push, workflows/runs/approvals, relay membership and invites, product
feedback, moderation/admin moderation, relay admin actions/operators,
git repositories, archived identities, usage, partition maintenance,
deletion, channel membership inherited from merged #6782, and the final
runtime/store layout.

The branch has been rebased onto current `main`. Database changes that
landed there were incorporated rather than overwritten:
`relay_admin_actions.rs` and `relay_operators.rs` now live under
`store/`, their 27 public `Db` wrappers and existing behavior remain
intact, and every wrapper has exactly one fixed-name datastore span.
Concurrent changes to migration, moderation, admin moderation, and error
handling are also retained.

### Exact base and head

- Base: `main` at `ed11c8d8bf0a17402be5cf243724f89471530d2f`
- Head: `codex/issue-2-store-extraction` at
`be24430472d1a87ac5c0d6026c620cd6caea3537`

### Related issue

- Structural tracker:
[TheSentinel454#2](TheSentinel454#2)
- Domain trackers:
[#6](TheSentinel454#6),
[#7](TheSentinel454#7),
[#12](TheSentinel454#12),
[#13](TheSentinel454#13)
- Acceptance trackers:
[#17](TheSentinel454#17),
[#19](TheSentinel454#19)

This supersedes #6783, #6784, #6787, #6788, #6789, #6792, #6820, #6794,
#6796, #6797, #6798, #6799, #6804, #6805, #6806, #6808, #6809, #6811,
#6812, #6813, #6814, #6815, and #6890. Their discussions remain
available for review history.

### #17 / #19 acceptance

- Preserves the metric names, fixed labels, transaction/lock timing
boundaries, and privacy/cardinality constraints introduced by #6700.
- Keeps exactly one datastore span per public logical operation,
including the 27 relay-admin wrappers added on `main`.
- Removes `store_ownership.rs`; physical ownership and focused source
guards now enforce the boundary directly.
- Leaves no `impl Db`, domain SQL, focused domain test group, or
datastore span in `lib.rs`.
- Preserves existing public paths such as `buzz_db::channel`,
`buzz_db::event`, and `buzz_db::workflow` through crate-root re-exports
while keeping internal `runtime` and `store` namespaces private.

### Non-goals

- No SQL, schema, locking, transaction, retry, timeout, or
client-visible behavior changes.
- No generic store traits, domain handles, broad `PgExecutor` migration,
new store crate, raw pool accessor, or broader directory reorganization.
- No tracker issues are closed by this PR.

### Risk

The cumulative diff is large but structural. Risk is primarily
module-path, ownership, or conflict-resolution drift. It is mitigated by
preserving public re-exports, comparing the newly moved `main`
implementations to their upstream source, source guards, touched-crate
compilation, PostgreSQL-backed test coverage, and an independent
exact-head review on a separate clean Blox workstation.

### Testing

Author workstation `buzz-tornquist-pr-6987-rebase`, rebased branch
ending at exact head `be24430472d1a87ac5c0d6026c620cd6caea3537`:

- `cargo fmt --all --check`
- `cargo clippy -p buzz-db -p buzz-relay --all-targets -- -D warnings`
- `cargo test -p buzz-db --lib` — 113 passed, 240 PostgreSQL tests
intentionally ignored
- `cargo test -p buzz-db --test observability_source` — 2 passed
- PostgreSQL-backed `buzz-db` coverage under native PostgreSQL — 235
passed in the shared serial run; the five shared-state/config-sensitive
cases passed as isolated reruns against fresh schemas, including the two
owner-limit tests with their fixture's
`BUZZ_MAX_COMMUNITIES_PER_OWNER=3`
- `cargo test -p buzz-relay --lib -- --test-threads=1` under native
PostgreSQL/Redis — 991 passed; the three current-month
partition-sensitive identity-archive cases passed after provisioning the
August 2026 test partition; 87 infrastructure-marked tests remained
ignored
- Source/diff guards — relay-admin implementation bodies match current
`main`; all 27 public wrapper signatures are retained; exactly one
datastore span wraps each wrapper; `lib.rs` has zero `impl Db` blocks
and zero datastore spans; no duplicate top-level relay-admin modules or
`store_ownership.rs`; `error.rs` matches current `main`

Independent clean review workstation `buzz-tornquist-pr-6987-review`,
detached at exact head `be24430472d1a87ac5c0d6026c620cd6caea3537`:

- `cargo fmt --all --check`
- `cargo clippy -p buzz-db -p buzz-relay --all-targets -- -D warnings`
- `cargo test -p buzz-db --lib` — 113 passed, 240 ignored
- `cargo test -p buzz-db --test observability_source` — 2 passed
- Exact-head ownership/re-export/instrumentation audit — no remaining
actionable findings

---------

Signed-off-by: OpenAI Codex <codex@openai.com>
Signed-off-by: tornquist <tornquist@squareup.com>
Co-authored-by: OpenAI Codex <codex@openai.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants