Capture lock waits during a synthetic concurrent workload
Reviewers need observations of a migration while ordinary writes continue.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- PostgreSQL · Concurrency
Estimated field mix
- Database engineering40%
- Performance engineering30%
- Developer tooling30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional subscription service has accumulated migration scripts with unclear lock risks and no consistent rehearsal output.
Setup prerequisites
- Create a disposable local database with synthetic subscriptions and a separate scratch database; author all fixtures locally.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Run bounded synthetic writes against the local fixture.
- Capture migration duration and sampled lock waits.
- Record dataset size and workload parameters with results.
Implementation constraints
- Set statement and lock timeouts; avoid extrapolating local results to production.
Verification to include
- Observe a compatible migration under writes.
- Force lock contention and verify timeout cleanup.
Deliverables
- Lock rehearsal report.
Rollout and recovery
Use reports for review; stop rehearsal on timeout and reset scratch data.
Value of the work
For the engineer: Practice migration tooling, lock reasoning, and clear developer feedback.
For the team: Provide reviewers with repeatable migration checks and explicit recovery limits.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.