3 ms·
disabled autovacuum by default I realize this wasn't their solution, but it's worth noting that generally speaking, disabling auto-vacuum isn't recommended. Ev
by utternerd 10y ago
disabled autovacuum by default
I realize this wasn't their solution, but it's worth noting that generally speaking, disabling auto-vacuum isn't recommended. Even if you do, it will still force vacuum jobs to prevent transaction ID wraparound.
* https://www.postgresql.org/docs/9.5/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND https://www.postgresql.org/docs/9.5/static/routine-vacuuming...
- kevinburke 10y agoAgreed, but if you are running a CI provider and recycling containers, seems easy enough to do it as part of the recycle step.
- utternerd 10y agoI agree it'd be a nice option for them to provide, but I don't believe making it the default for every customer is a laudable goal. If vacuums are hanging/causing locks and these truly are just test tables, it might be beneficial to use temporary tables instead as the autovacuum daemon ignores them. Additionally, unlogged tables that reside on a memory disk can be insanely fast - might cut some additional time down depending on your data.