Re: VACUUM FULL out of memory - Mailing list pgsql-hackers

From Usama Dar
Subject Re: VACUUM FULL out of memory
Date
Msg-id ff0e67090801070700h5efa4f86qd645bfe959698df6@mail.gmail.com
Whole thread Raw
In response to Re: VACUUM FULL out of memory  (Michael Akinde <michael.akinde@met.no>)
Responses Re: VACUUM FULL out of memory  (Michael Akinde <michael.akinde@met.no>)
List pgsql-hackers


On Jan 7, 2008 2:40 PM, Michael Akinde <michael.akinde@met.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

pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: [BUGS] BUG #3852: Could not create complex aggregate
Next
From: "Kevin Grittner"
Date:
Subject: Re: OUTER JOIN performance regression remains in 8.3beta4