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. Packers 73.9K posts
- 2. Rob Reiner 9,288 posts
- 3. #ITWelcomeToDerry 17K posts
- 4. Broncos 66.7K posts
- 5. Parsons 31.3K posts
- 6. JJ McCarthy 3,685 posts
- 7. Mahomes 79.6K posts
- 8. Rams 29.4K posts
- 9. #Married2Med 1,931 posts
- 10. #BaddiesUSA 8,550 posts
- 11. Bo Nix 15.6K posts
- 12. Chiefs 161K posts
- 13. Lions 54.3K posts
- 14. Panthers 30.7K posts
- 15. Colts 39.3K posts
- 16. Saints 34.2K posts
- 17. Vikings 17.6K posts
- 18. Watson 20.4K posts
- 19. Happy Hanukkah 34.5K posts
- 20. Seahawks 36.8K posts
Loading...
Something went wrong.
Something went wrong.