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 Tendencias
- 1. Knicks 78.8K posts
- 2. Mariah 29.6K posts
- 3. NBA Cup 63K posts
- 4. Clarkson 8,721 posts
- 5. Spurs 48.8K posts
- 6. Tyler Kolek 7,449 posts
- 7. Wemby 27.4K posts
- 8. #NewYorkForever 4,788 posts
- 9. Buck Rogers 3,034 posts
- 10. Thug 23.2K posts
- 11. #MightyNeinSpoilers N/A
- 12. Josh Hart 6,075 posts
- 13. Brunson 24.4K posts
- 14. Mitch 15.8K posts
- 15. Gil Gerard 2,980 posts
- 16. #LMD7 53.1K posts
- 17. Thea 13.9K posts
- 18. Mike Brown 4,909 posts
- 19. thalia 2,539 posts
- 20. Thibs 1,062 posts
Loading...
Something went wrong.
Something went wrong.