Truncate vs. Delete: Efficiently Clearing Data from a Postgres Table

Re:Truncate vs. Delete: Efficiently Clearing Data from a Pos... by adeel_siddiqui on Tuesday July 30, 2019 @10:31AM (#20565142)

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.

[ Parent | on HN ]

Re:Truncate vs. Delete: Efficiently Clearing Data from a Pos... by mgartner on Tuesday July 30, 2019 @09:56PM (#20571086)

You'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.

[ Parent | on HN ]