You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Migration ActivityLogSeq0000000029000 locks activity_logs for its whole run. It adds activity_logs.seq and backfills every existing row in one transaction, holding an ACCESS EXCLUSIVE lock from the ADD COLUMN through the backfill, SET NOT NULL and the unique index build. Nothing can read or write activity_logs meanwhile, and every submit, decision and history read touches it, so on a large table plan the run as downtime in a maintenance window. lock_timeout bounds only the wait to take the lock, not how long it is held.
Run it inside a transaction (the default) and before serving 0.17.5.
The backfill rewrites every row: leave free disk for roughly another copy of the table plus its WAL, and run VACUUM (ANALYZE) activity_logs afterwards.
🚀 Features
workflow-engine: record the write order of activity logs (d3a946a)
🩹 Fixes
organization: let template designers read the organization (4f76202)
organization: open only the designer's three organization reads (28b5146)
workflow-engine: read activity logs in write order (4b9865f)