3 ms·
Good point. If you are doing this, you also need a good autovacuuming strategy on your pg database. Depending on the size of the tables and the frequency of DEL
by adeel_siddiqui 7y ago
Good point. If you are doing this, you also need a good autovacuuming strategy on your pg database. Depending on the size of the tables and the frequency of DELETEs, not vacuuming regularly could potentially cause problems like bloated size on disk, slow queries, etc.
- mgartner 7y agoYou're totally right. In our case, our test infrastructure spins up a new Postgres container for every build. Because it's not a long-running database, bloat is not a concern.