mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-07 04:12:04 +00:00
Roles are cluster-wide. Two HealthLog databases on one server shared healthlog_app: each start set its own password, locking the other instance out, and the role held grants on both databases. The role is now healthlog_app_<database>_<hash>, marked with a comment naming its database, its password is derived per database, and a role holding an explicit CONNECT on another database is not used. The role owned the pgboss schema, so it could plant a trigger, a rule or a function body that a later owner session (a rollback, DB_APP_ROLE=off, a fallback start) would run with the owner's rights. pg-boss changes its schema only on install, on migration and for partitioned queues, which the app does not use. The start now installs and migrates the schema as the owner with pg-boss's own plans, and the worker runs pg-boss with migrate: false when it does not own the schema. The role gets rows only, read-only on pgboss.bam (SQL the migration runner executes) and on the version column. Every start, on every path, takes back what a HealthLog role owns there, drops triggers and rules, and after a take-back restores the queue functions to pg-boss's own definitions and retires the legacy role. Bloated queue indexes, which pg-boss only reports when it does not own them, are rebuilt at start.