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. Bondi Beach 185K posts
- 2. Hanukkah 68.1K posts
- 3. Gunther 94K posts
- 4. Spurs 73.7K posts
- 5. Naveed Akram 16.4K posts
- 6. John Cena 584K posts
- 7. Good Sunday 58.9K posts
- 8. #SNME 303K posts
- 9. #ThankYouCena 465K posts
- 10. Brown University 235K posts
- 11. Triple H 103K posts
- 12. Wemby 52.6K posts
- 13. Chanukah 16.6K posts
- 14. Chrisean 7,588 posts
- 15. TOP CALL 6,529 posts
- 16. #JungkookxElleKorea 81.6K posts
- 17. Chet 17.4K posts
- 18. Rhode Island 57.4K posts
- 19. Caruso 8,207 posts
- 20. #UFCVegas112 22K posts
Loading...
Something went wrong.
Something went wrong.