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. Epstein 529K posts
- 2. Elise Stefanik 5,602 posts
- 3. Rays 14.7K posts
- 4. Michael Jackson 18.2K posts
- 5. Randy Moss 5,747 posts
- 6. Lamarr Wilson 2,217 posts
- 7. Shane Baz 3,617 posts
- 8. Kennedy Center 178K posts
- 9. Jake Paul 33.2K posts
- 10. Tucker 187K posts
- 11. Dashie N/A
- 12. timmy tim N/A
- 13. The DOJ 110K posts
- 14. Pirates 19.8K posts
- 15. EsDeeKid 4,470 posts
- 16. Sought 18.4K posts
- 17. Lowe 9,517 posts
- 18. Bowen Yang 3,226 posts
- 19. Happy Holidays 52.3K posts
- 20. Oklahoma 28.7K posts
Loading...
Something went wrong.
Something went wrong.