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 Tendances
- 1. Knicks 80.1K posts
- 2. Mariah 31K posts
- 3. #MightyNeinSpoilers 1,065 posts
- 4. NBA Cup 64.3K posts
- 5. Spurs 49.2K posts
- 6. Buck Rogers 3,473 posts
- 7. #TAEHYUNGxCELINE 43.2K posts
- 8. #NewYorkForever 4,853 posts
- 9. Tyler Kolek 7,572 posts
- 10. thalia 2,825 posts
- 11. Thug 24.2K posts
- 12. Josh Hart 6,307 posts
- 13. Gil Gerard 3,410 posts
- 14. Brunson 25K posts
- 15. Wemby 27.6K posts
- 16. Mitch 16K posts
- 17. #LMD7 53.7K posts
- 18. Thea 14.2K posts
- 19. #MAGMA 1,318 posts
- 20. Thibs 1,073 posts
Loading...
Something went wrong.
Something went wrong.