Use Optimistic Locking with a Version Column
Add a version column and check it on update so concurrent edits are detected and the last writer gets a 409 not a silent overwrite.
Task
Apply UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3; so the schema change is safe, reversible, and does not lock the table during peak traffic.
When to use this
A migration deploys UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3; during peak hours, takes a 40-second lock, and causes a connection pool exhaustion.
Prerequisites
- A database with migration tooling configured
- A staging environment mirroring production schema
Steps
1. Configure UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3; in the project configuration file with the recommended defaults.
UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3;
Expected output: The configuration is accepted and UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3; runs without errors on the first invocation.
2. Run the check locally to verify UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3; produces the expected result before pushing.
pnpm test
Expected output: Local run matches CI behavior; no surprises after push.
3. Add the gate to the CI pipeline so UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3; blocks merge on failure.
- name: Run add optimistic lock version
run: pnpm test
Expected output: Pull requests with failing UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3; are blocked from merging.
Troubleshooting
Problem
The check passes locally but fails in CI
Solution
Pin dependency versions and the runtime to match CI exactly; reproduce with the same Docker image or act.
Problem
Configuration is rejected with a schema error
Solution
Check the tool version matches the config schema; older versions may not support newer fields.
Limitations
- The gate only runs on events that trigger the workflow; locally pushed commits bypass it.
- Configuration drift is possible if someone edits settings outside version control.
Make migrations safe
Start by measuring the problem. Add a version column and check it on update so concurrent edits are detected and the last writer gets a 409 not a silent overwrite. The most common mistake is adding the gate without first confirming it catches the issue you care about. Run UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3; against the current codebase and inspect the output before wiring it into CI.
UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3;Verify and roll back
Once the gate is in place, make failures actionable. A failing UPDATE docs SET body = $1, version = version + 1 WHERE id = $2 AND version = $3; should point to the exact file and line, not a generic error. Pin the tool version in the lockfile so a upstream release does not silently change behavior. Review the gate output in every pull request just like a test result.