Postgres Pro
Downloads
Home   >   mailing lists

Re: After how many updates should a vacuum be performed? - Mailing list pgsql-admin

From Tom Lane
Subject Re: After how many updates should a vacuum be performed?
Date
Msg-id 13915.1158168441@sss.pgh.pa.us
Whole thread Raw
In response to Re: After how many updates should a vacuum be performed?  (Ellen Cyran <ellen@urban.csuohio.edu>)
Responses Re: After how many updates should a vacuum be performed?  (Ellen Cyran <ellen@urban.csuohio.edu>)
Re: After how many updates should a vacuum be performed?  (Ellen Cyran <ellen@urban.csuohio.edu>)
List pgsql-admin
Tree view 
Ellen Cyran <ellen@urban.csuohio.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

pgsql-admin by date:

Previous
From: Ellen Cyran
Date:
Subject: Re: After how many updates should a vacuum be performed?
Next
From: Ellen Cyran
Date:
Subject: Re: After how many updates should a vacuum be performed?