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. Chiefs 107K posts
- 2. Mahomes 41K posts
- 3. Bills 136K posts
- 4. Philip Rivers 23.8K posts
- 5. Patriots 130K posts
- 6. Josh Allen 27.5K posts
- 7. Chargers 63.3K posts
- 8. Rams 14.2K posts
- 9. Pats 22.5K posts
- 10. Seahawks 20.8K posts
- 11. Australia 1.57M posts
- 12. Broncos 32.5K posts
- 13. Josh Jacobs 6,843 posts
- 14. Drake Maye 26.3K posts
- 15. Raiders 36.8K posts
- 16. Browns 39.1K posts
- 17. #OnePride 4,247 posts
- 18. Goff 4,959 posts
- 19. Shedeur 31.4K posts
- 20. Bengals 31.4K posts
Loading...
Something went wrong.
Something went wrong.