On Tue, Aug 9, 2016 at 1:02 AM, Binand Sethumadhavan <binand@gmx.net> wrote:
> Several months back, we started noticing slow inserts to these tables
> (and high load average on the DB server), and eventually traced the
> problem to the autovacuum process. As a workaround, we started
> disabling autovacuum during our peak load times. We run from cron:
> ALTER TABLE table_name SET (autovacuum_enabled = FALSE) to disable and
> once our concurrent player count starts going down, set
> autovacuum_enabled to TRUE to enable it.
I have found it safer and more effective to leave autovacuum
running at all times and add VACUUM ANALYZE commands during the off
peak hours. This will prevent autovacuum from kicking in during
peak load periods unless there is, for example, a large number of
updates to a small table -- in which case the autovacuum run will
normally be pretty quick and will prevent a slowdown. Of course,
you may need to run autovacuum a bit, too; but there aren't enough
clues here to suggest anything specific.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company