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. #Survivor49 12.4K posts
- 2. #PresidentialAddress 14.1K posts
- 3. Savannah 16.7K posts
- 4. #AEWDynamite 22K posts
- 5. Kristina 4,681 posts
- 6. Venezuela 918K posts
- 7. Disturbed 6,112 posts
- 8. Jake Allen N/A
- 9. Newt 1,886 posts
- 10. Rizo 1,966 posts
- 11. Cavs 7,379 posts
- 12. #SistasOnBET 2,422 posts
- 13. Sophi 2,018 posts
- 14. Warrior Dividend 24.6K posts
- 15. Adderall 5,124 posts
- 16. #AdamKutnerPowerPlay N/A
- 17. Delaware 6,075 posts
- 18. Garfunkel N/A
- 19. Randle 4,731 posts
- 20. Kevin Warren 2,706 posts
Loading...
Something went wrong.
Something went wrong.