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 Trends
- 1. #doordashfairy 1,171 posts
- 2. Vanity Fair 67K posts
- 3. Susie Wiles 133K posts
- 4. Mustapha Kharbouch 31.7K posts
- 5. Mick Foley 34.6K posts
- 6. Mary and Joseph 2,090 posts
- 7. Olive Garden 1,351 posts
- 8. Larian 12K posts
- 9. Brookline 10.8K posts
- 10. Snowslingers N/A
- 11. Christensen 5,932 posts
- 12. Penguins Christmas Party Time N/A
- 13. Brand New Day 11.1K posts
- 14. Michelea Ponce 36.8K posts
- 15. Firefox 5,931 posts
- 16. $TSLA 51.4K posts
- 17. Cardiff 29.2K posts
- 18. Kay Flock 1,436 posts
- 19. Carville 3,756 posts
- 20. Gittens 7,983 posts
Loading...
Something went wrong.
Something went wrong.