All true. The way the VACUUM truncation works confuses people sometimes. The database has to exclusive lock the very last page of the table to shrink the file. It does that over and over again, until it finds a page that's still live.
VACUUM can truncate empty pages at the end of a table but doesn't do the same for indexes.
Yes, an access-exclusive lock is needed for truncation. Since some users may prefer to avoid this, I implemented the "vacuum_truncate" storage parameter, allowing them to choose whether truncation should occur.
United States الاتجاهات
- 1. Lamar 21.8K posts
- 2. Ravens 35.6K posts
- 3. Steelers 77.1K posts
- 4. Mark Andrews 4,051 posts
- 5. Lions 86.9K posts
- 6. Drake Maye 8,222 posts
- 7. #Married2Med 3,320 posts
- 8. Derrick Henry 4,428 posts
- 9. Toya 5,484 posts
- 10. #RHOP 5,743 posts
- 11. Henderson 12K posts
- 12. Jags 16K posts
- 13. Zay Flowers 2,073 posts
- 14. Tyler Huntley 1,351 posts
- 15. Broncos 37.5K posts
- 16. #BaddiesUSA 5,705 posts
- 17. #HereWeGo 9,377 posts
- 18. #Patriots 3,492 posts
- 19. Contreras 11K posts
- 20. Goff 9,100 posts
Loading...
Something went wrong.
Something went wrong.