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 Tendências
- 1. The JUP 441K posts
- 2. FINALLY DID IT 443K posts
- 3. Greg Biffle 7,304 posts
- 4. Statesville 8,357 posts
- 5. Jason Kidd 1,388 posts
- 6. NextNRG 2,405 posts
- 7. Hunger Games 5,739 posts
- 8. #DareYouToDeathEP1 1.13M posts
- 9. Helene 5,591 posts
- 10. Zollers N/A
- 11. #thursdayvibes 3,524 posts
- 12. Skenes 4,305 posts
- 13. #NicolandriaxGlamour 11K posts
- 14. Xbox controller 1,341 posts
- 15. Team USA 7,078 posts
- 16. Kerry Kittles N/A
- 17. Inflation 154K posts
- 18. Beau Pribula N/A
- 19. Baugh 1,661 posts
- 20. High Noons N/A
Loading...
Something went wrong.
Something went wrong.