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. Rob Reiner 275K posts
- 2. Good Monday 34.7K posts
- 3. All in the Family 29.4K posts
- 4. Meathead 8,131 posts
- 5. #ITWelcomeToDerry 175K posts
- 6. #MondayMotivation 6,786 posts
- 7. The Princess Bride 19.3K posts
- 8. Stand By Me 22.5K posts
- 9. When Harry Met Sally 22.8K posts
- 10. Cowboys 38.8K posts
- 11. Brentwood 21.3K posts
- 12. Spinal Tap 18.9K posts
- 13. Chile 776K posts
- 14. Brooks 33.9K posts
- 15. Pennywise 65.9K posts
- 16. Ella Cook 28.5K posts
- 17. Shaq 5,790 posts
- 18. LAPD 9,908 posts
- 19. Richie 39K posts
- 20. Rest in Peace 57.3K posts
Loading...
Something went wrong.
Something went wrong.