Background
PR #1037 chose per-row CAS (TransitionExecutionStatus) for atomic claim-then-execute. Intentional and sound design.
GetPendingExecutionsTx was written for an alternative serialisable-transaction design that was superseded.
Problem
GetPendingExecutionsTx (and its tx-based locking scaffolding) became dead code after #1037 landed.
Options
- Remove if confirmed dead.
- Document as future hook for batch-claim scenarios.
Note
The #1037 CAS choice is intentional and sound. Do not revisit without a separate ADR. This chore is purely cleanup.
Files: internal/config/store_postgres.go (GetPendingExecutionsTx)
Background
PR #1037 chose per-row CAS (TransitionExecutionStatus) for atomic claim-then-execute. Intentional and sound design.
GetPendingExecutionsTx was written for an alternative serialisable-transaction design that was superseded.
Problem
GetPendingExecutionsTx (and its tx-based locking scaffolding) became dead code after #1037 landed.
Options
Note
The #1037 CAS choice is intentional and sound. Do not revisit without a separate ADR. This chore is purely cleanup.
Files: internal/config/store_postgres.go (GetPendingExecutionsTx)