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. FINALLY DID IT 599K posts
- 2. The BONK 166K posts
- 3. The JUP 155K posts
- 4. Quinn Ewers 3,873 posts
- 5. Mariah 45.8K posts
- 6. #SantaChat N/A
- 7. Algorhythm Holdings N/A
- 8. Robert E Lee 16.3K posts
- 9. Judon N/A
- 10. Jack Smith 16.5K posts
- 11. #wednesdaymotivation 2,645 posts
- 12. Good Wednesday 37.8K posts
- 13. #SomosBolivarianos 2,486 posts
- 14. #NoWarYesPeace 3,717 posts
- 15. #keyboard 3,366 posts
- 16. Fani Willis 2,695 posts
- 17. QB Tua Tagovailoa 2,997 posts
- 18. Zach Wilson 1,027 posts
- 19. Hump Day 16.9K posts
- 20. Thug 30.4K posts
Loading...
Something went wrong.
Something went wrong.