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 Trendy
- 1. FINALLY DID IT 622K posts
- 2. The JUP 180K posts
- 3. The PENGU 227K posts
- 4. The BONK 170K posts
- 5. Good Tuesday 32.6K posts
- 6. #PersonOfTheYearAwards2025 475K posts
- 7. Alex Delgado N/A
- 8. #riddle 3,715 posts
- 9. #amulet 3,207 posts
- 10. #MAGMA N/A
- 11. #jovian 3,443 posts
- 12. Namjoon 86.7K posts
- 13. DataHaven 26K posts
- 14. OT7 LIVE 41.8K posts
- 15. Rodman 1,623 posts
- 16. TOP CALL 8,602 posts
- 17. Jokic 11.9K posts
- 18. The BBC 117K posts
- 19. Rockets 16.9K posts
- 20. Sengun 6,230 posts
Loading...
Something went wrong.
Something went wrong.