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. #doordashfairy 1,050 posts
- 2. Vanity Fair 60.7K posts
- 3. Susie Wiles 123K posts
- 4. Mick Foley 32.7K posts
- 5. Mustapha Kharbouch 19.8K posts
- 6. Olive Garden 1,101 posts
- 7. Larian 10.7K posts
- 8. Brookline 8,812 posts
- 9. $TSLA 48.8K posts
- 10. Michelea Ponce 31.6K posts
- 11. Cardiff 24.4K posts
- 12. Christensen 2,936 posts
- 13. Kay Flock N/A
- 14. Carville 3,192 posts
- 15. Gittens 7,157 posts
- 16. Spielberg 28.6K posts
- 17. Tosin 8,814 posts
- 18. Mary and Joseph 1,270 posts
- 19. #SpiderManBrandNewDay 1,645 posts
- 20. Garnacho 16.2K posts
Loading...
Something went wrong.
Something went wrong.