I apologize for my original post being unclear. I'm running "vacuum analyze" and seeing the behavior mentioned. Does specifying the analyze option imply "vacuum full"?
On a hunch I just ran analyze <really big table> and the backend's memory usage soared up to 100+ megs. I suspect that means it isn't the vacuum but the analyze that is eating all my precious ram. :) Any tips on minimizing the memory footprint during analyze (ie: backing off the 300 setting that I'm currently using) or is this just something I'll have to live with? Regards, Shelby Cain --- Tom Lane <[EMAIL PROTECTED]> wrote: > > Don't use VACUUM FULL. The vacuum_mem setting only > limits the space > consumed by plain VACUUM --- VACUUM FULL needs to > keep track of all the > free space in the table, and will eat as much memory > as it has to to do > that. > > regards, tom lane __________________________________ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
