Setting vacuum_mem for vacuumdb utility

[Jeff Boes]

I just discovered that the use of a much larger setting on vacuum_mem
has a joyous effect on the throughput of VACUUM FULL for some of our
tables. However, all of my maintenance scripts use "vacuumdb" (the
command-line utility) instead of psql. How can I set vacuum_mem for the
duration of the vacuumdb command's execution?

[Bruce Momjian]

Post by Jeff Boes
I just discovered that the use of a much larger setting on vacuum_mem
has a joyous effect on the throughput of VACUUM FULL for some of our
tables. However, all of my maintenance scripts use "vacuumdb" (the
command-line utility) instead of psql. How can I set vacuum_mem for the
duration of the vacuumdb command's execution?

Sure, set it in postgresql.conf.

[Chris Hoover]

Post by Bruce Momjian

Post by Jeff Boes
I just discovered that the use of a much larger setting on vacuum_mem
has a joyous effect on the throughput of VACUUM FULL for some of our
tables. However, all of my maintenance scripts use "vacuumdb" (the
command-line utility) instead of psql. How can I set vacuum_mem for the
duration of the vacuumdb command's execution?

Sure, set it in postgresql.conf.

You can also modify the vacuumdb script. I just added a set call to the
script to set the memory to a high value when vacuuming and reset it
back to normal when finished so I don't take extra memory away from the
server.


---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html