Skip to content

Add ADR-002: Explicit timeout required for all lock operations#23

Merged
antonkomarev merged 1 commit into
masterfrom
feature/adr-004-explicit-timeout
Feb 8, 2026
Merged

Add ADR-002: Explicit timeout required for all lock operations#23
antonkomarev merged 1 commit into
masterfrom
feature/adr-004-explicit-timeout

Conversation

@antonkomarev
Copy link
Copy Markdown
Member

  • All lock acquisition methods MUST require explicit TimeoutDuration parameter
  • No default timeout, no 'wait forever' convenience methods
  • Production safety: prevents accidental infinite waits
  • Self-documenting code: timeout value signals expected lock contention
  • Consistent with PostgreSQL best practices

@antonkomarev antonkomarev force-pushed the feature/adr-004-explicit-timeout branch from 974ec70 to f893baf Compare February 8, 2026 16:30
- All lock acquisition methods MUST require explicit TimeoutDuration parameter
- No default timeout, no 'wait forever' convenience methods
- Production safety: prevents accidental infinite waits
- Self-documenting code: timeout value signals expected lock contention
- Consistent with PostgreSQL best practices
@antonkomarev antonkomarev force-pushed the feature/adr-004-explicit-timeout branch from f893baf to 9721ab0 Compare February 8, 2026 16:31
@antonkomarev antonkomarev changed the title Add ADR-004: Explicit timeout required for all lock operations Add ADR-002: Explicit timeout required for all lock operations Feb 8, 2026
@antonkomarev antonkomarev merged commit 181a190 into master Feb 8, 2026
2 checks passed
@antonkomarev antonkomarev deleted the feature/adr-004-explicit-timeout branch February 8, 2026 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant