From: | "Usama Dar" <munir(dot)usama(at)gmail(dot)com> |
---|---|
To: | "Michael Akinde" <michael(dot)akinde(at)met(dot)no> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: VACUUM FULL out of memory |
Date: | 2008-01-07 15:00:05 |
Message-ID: | ff0e67090801070700h5efa4f86qd645bfe959698df6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jan 7, 2008 2:40 PM, Michael Akinde <michael(dot)akinde(at)met(dot)no> wrote:
> As suggested, I tested a VACUUM FULL ANALYZE with 128MB shared_buffers
> and 512 MB reserved for maintenance_work_mem (on a 32 bit machine with 4
> GB RAM).
My Apologies if my question seems redundant and something you have already
discussed with list members, but why do you need to do a VACUUM FULL? have
you not vacuumed for a while? or some special requirement which requires
very aggressive space re-claim? Vacuum Full is also known to cause some
index bloat at times as well. most systems i know run regular vacuums and
had never required to run a vacuum full.
--
Usama Munir Dar http://www.linkedin.com/in/usamadar
Consultant Architect
Cell:+92 321 5020666
Skype: usamadar
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2008-01-07 15:01:50 | Re: OUTER JOIN performance regression remains in 8.3beta4 |
Previous Message | Joe Conway | 2008-01-07 14:59:51 | Re: BUG #3852: Could not create complex aggregate |