Re: VACUUM FULL out of memory
| От | Usama Dar |
|---|---|
| Тема | Re: VACUUM FULL out of memory |
| Дата | |
| Msg-id | ff0e67090801070700h5efa4f86qd645bfe959698df6@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: VACUUM FULL out of memory (Michael Akinde <michael.akinde@met.no>) |
| Ответы |
Re: VACUUM FULL out of memory
|
| Список | pgsql-hackers |
On Jan 7, 2008 2:40 PM, Michael Akinde <michael.akinde@met.no> wrote:
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.
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 по дате отправления: