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. Sam Darnold 10.8K posts
- 2. Rams 49.3K posts
- 3. Portuguese 19.6K posts
- 4. Stafford 11.8K posts
- 5. Kenneth Walker 3,097 posts
- 6. Puka 33.7K posts
- 7. Shaheed 4,155 posts
- 8. Cooper Kupp 1,995 posts
- 9. Seattle 21K posts
- 10. Portugal 44.7K posts
- 11. Al Michaels N/A
- 12. Kubiak 1,598 posts
- 13. McVay 3,603 posts
- 14. Ben Shapiro 24.2K posts
- 15. #LARvsSEA 1,640 posts
- 16. Pelicans 2,642 posts
- 17. Chris Shula N/A
- 18. #TNFonPrime 2,967 posts
- 19. Claudio Manuel Neves-Valente 3,869 posts
- 20. New Hampshire 18.1K posts
Loading...
Something went wrong.
Something went wrong.