Re: After how many updates should a vacuum be performed?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ellen Cyran <ellen(at)urban(dot)csuohio(dot)edu>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: After how many updates should a vacuum be performed?
Date: 2006-09-13 17:27:21
Message-ID: 13915.1158168441@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Ellen Cyran <ellen(at)urban(dot)csuohio(dot)edu> writes:
>> Hm, that should be OK. What do you have maintenance_work_mem set to?

> It's set at the default 16384.

That should be plenty for getting rid of a million or so tuples. I'm
wondering if you are seeing some weird locking effect. Is the VACUUM
constantly busy with I/O or does it sit and wait at points? Do you have
other queries actively accessing the table during the VACUUM?

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ellen Cyran 2006-09-13 18:07:23 Re: After how many updates should a vacuum be performed?
Previous Message Ellen Cyran 2006-09-13 17:11:42 Re: After how many updates should a vacuum be performed?