This website uses cookies to ensure you get the best experience.
Learn more.
A proposed clustering change improves one query but creates ongoing maintenance cost. What should determine adoption?
Published
- Only whether the key has the longest name
- Measured workload-wide benefit relative to maintenance cost
- Only the shortest single observed runtime
- A belief that all large tables require manual clustering
Comments — 0
Sign in to comment