awslabs / awslabs/amazon-redshift-utils
min_block_sec and max_block_sec aggregate different measures
Open
- Dominant language
- Python
- Stars
- 2.8k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/awslabs/amazon-redshift-utils/blob/bfe6b021e3c292723f52e4c7f81c5278e37737c4/src/AdminViews/v_get_blocking_locks.sql#L64
Is this really correct? Why use transaction time for one and waiting time for the other? annotations on this view would be great, because I don't understand it well enough to know if it is correct.
Contributor guide
Research direction
Open src/AdminViews/v_get_blocking_locks.sql at line 64 and compare the measures used by min_block_sec and max_block_sec. Read the surrounding view definition and Amazon Redshift locking and transaction semantics first; done means the issue has a documented rationale and any necessary correction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100