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 280K posts
- 2. Good Monday 35.4K posts
- 3. All in the Family 29.7K posts
- 4. Meathead 8,290 posts
- 5. #MondayMotivation 6,908 posts
- 6. The Princess Bride 19.6K posts
- 7. #ITWelcomeToDerry 176K posts
- 8. Stand By Me 22.9K posts
- 9. When Harry Met Sally 23.2K posts
- 10. Cowboys 39K posts
- 11. Spinal Tap 19.1K posts
- 12. Brentwood 21.4K posts
- 13. Chile 784K posts
- 14. Pennywise 66.6K posts
- 15. Shaq 5,834 posts
- 16. Ella Cook 29.1K posts
- 17. Brooks 34.1K posts
- 18. Richie 39.4K posts
- 19. LAPD 10K posts
- 20. Rest in Peace 58.2K posts
Loading...
Something went wrong.
Something went wrong.