delongboy <sdelong@saucontech.com> wrote:
> We are not doing anything to postgres that would cause the rise
> and drop. Data base activity is pretty consistent. nor are we
> doing any kind of purge. This week the drop occurred after 6
> days. We are thinking it must be some kind of internal postgres
> activity but we can't track it down.
Maybe autovacuum freezing tuples (which is a WAL-logged operation)
as tables periodically hit the autovacuum_freeze_max_age limit?
-Kevin