mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Marc-André Bombeck
5e66ebaa54
The nightly tombstone purge asked for `deleted_at IS NOT NULL AND deleted_at < cutoff` and the audit-log purge asked for `created_at < cutoff`. Neither predicate had an index behind it: every deleted_at index in the schema is partial on IS NULL, the live-rows predicate, and every audit_logs index leads with user_id or action. Both purges planned a sequential scan and then paid index maintenance per removed row, in one unbounded statement, on a connection carrying statement_timeout=60000. Past a certain backlog the statement aborts, the transaction rolls back, nothing is purged, and the next night runs the identical statement against the same rows. The mechanism that gives deletion a horizon could not close on the instances that needed it. Migration 0277 adds the indexes the predicates ask for; the three tombstone ones are partial on IS NOT NULL, so on a healthy instance they cover only the tombstones and shrink as the purge drains. The purges now walk the backlog in batches of 5 000 by primary key, capped at 200 000 rows a run. Both handlers used to swallow every error into a wide-event warning and return, so pg-boss recorded a successful job either way: a purge failing every night looked exactly like a purge with nothing to do. They now rethrow, and a run that stops at the cap records that a backlog remains.
prisma/
The database layer. HealthLog runs PostgreSQL 16 via Prisma 7. This directory holds the single schema file and the forward-only migration history; the generated client is emitted elsewhere.
Contents
schema.prisma— 61 models, one file.cuid()primary keys,snake_casecolumns via@map(...), encrypted columns mostly suffixed*Encrypted(search the file; there are 24 encrypted column references). Thegenerator clientblock emits to../src/generated/prisma(imported as@/generated/prisma).migrations/— numbered, forward-only SQL migrations (0001_…upward).migration_lock.tomlpins the provider topostgresql.
Migration workflow
# author a migration from a schema edit
pnpm dlx prisma migrate dev --name <short_snake_case_name>
# regenerate the client after any schema change
pnpm dlx prisma generate
Number a new migration with the next free prefix. The production entrypoint runs prisma migrate deploy on boot, so every migration must apply cleanly forward — there is no down-migration path. Always include the migration file in the same change as the schema edit.
Conventions
- Encryption is fail-closed:
*Encryptedcolumns are written through@/lib/crypto(AES-256-GCM, versioned key ids); never store plaintext in an encrypted column. Key rotation isscripts/rotate-encryption-key.ts+docs/ops/encryption-key-rotation.md. - The generated client under
src/generated/prismais build output — do not edit it. - Schema-touching changes that affect the API surface must regenerate
docs/api/openapi.yaml(see../CLAUDE.md).
Related: ../src/lib/README.md (db.ts, rollups/), ../docs/ops/ (migrations + backup runbooks).