Erik Jones escribió: > On Aug 28, 2007, at 4:33 PM, Marko Kreen wrote: > >> I've experienced something similar. The reason turned out to be >> combination of overcommit=off, big maint_mem and several parallel >> vacuums for fast-changing tables. Seems like VACUUM allocates >> full maint_mem before start, whatever the actual size of the table. >> >> Fix was to put "set maint_mem=32M" before small vacuums and >> serialize some of them. > > I'm not sure about the OP but I know that we just run autovacuum so no > problem with parallel vacuums. In addition, Solaris doesn't have > overcommit. Note that as of 8.3 you will have vacuums running in parallel with autovac ... 3 in the default config. So keep an eye on that maintenance_work_mem setting. -- Alvaro Herrera http://www.amazon.com/gp/registry/5ZYLFMCVHXC "XML!" Exclaimed C++. "What are you doing here? You're not a programming language." "Tell that to the people who use me," said XML. ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
