On 10/29/2015 2:43 PM, Jim Longwill wrote:
> Ok. The reason I wanted to experiment with autovacuum disable for
> 'ddev2' database is that it is a mostly read-only database -- to
> support querying from our web apps. I.e. there are only 1 or 2 small
> tables ever updated all day on it, and only about 20 or so records
> total per day (compared to 'ddev1' which has much more frequent
> activity). Also, it's rebuilt periodically from the other db, so I
> had the idea that we didn't need autovacuum running for 'ddev2'.
>
> However, given that it is connected to the Postgres processes
> (launcher) and I can't turn it off per database, it may not be worth
> the trouble to configure this. I plan to experiment with other
> parameters as well, but this is not critical at this time.
autovacuum of tables that have already been vacuumed and have no changes
is essentially a no-op, it checks some stats and moves on to another table.
--
john r pierce, recycling bits in santa cruz
