Niek Otten 80d0308de8 fix(projection): serialise concurrent migrators with a pg advisory lock (refs #75) ...

verify-up failed: the event-subscriber and projection-api both migrate the shared
projection DB on start, and EF releases its migrations-history lock between individual
migrations — harmless with one migration, but the new AddNotificationResource made a
second, so a migrator re-applied it in the window between the other's two migrations
("column resource already exists"). Hold a session pg_advisory_lock across the whole
MigrateAsync so the sequence runs exactly once; the second migrator then finds nothing
pending.

Verified by starting both images simultaneously against a fresh Postgres: both reach
health, the resource column is created once, and __EFMigrationsHistory has both rows.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-14 10:03:14 +02:00

..

Projection.ReadModel

fix(projection): serialise concurrent migrators with a pg advisory lock (refs #75)

2026-07-14 10:03:14 +02:00

ProjectionApi.Api

fix(projection): serialise concurrent migrators with a pg advisory lock (refs #75)

2026-07-14 10:03:14 +02:00

Dockerfile

ci(infra): run the Event Subscriber + projection-api in compose and verify end-to-end (refs #7)

2026-06-30 15:11:24 +02:00