What are the circumstances where autovacuum can be disabled?
I have a table where I am performing only inserts, never deletes/updates.
I notice sometimes that autovacuum runs on this table, even though this is
the case.
autovacuum: VACUUM ANALYZE public.twitter_shares (to prevent wraparound)
It is taking a long time, and it is having an impact on the performance of
my DB. Is it safe for me to just disable autovacuum for this table? Since
I am not performing deletes/updates, I don't understand why autovacuum is
even needed, and why postgres decides to run it.
No comments:
Post a Comment