On 5/14/23 12:45, Wells Oliver wrote:
Noticed over the last few days how much more space VACUUM FULL reclaims (for obvious reasons) and I am wondering if there are any solutions for a more fruitful VACUUM without the locks of FULL?
Another tactic for UPDATE-heavy environments is to reduce the table's fillfactor. As long as an indexed field isn't modified, Postgresql will try and use in-place updates of these HOT (Heap Only Tuple) records.
-- Born in Arizona, moved to Babylonia.