All, Tuesday, January 22, 2002, 12:06:41 AM, you wrote:
KM> Yes, it seems to be a cache problem, [] KM> Also it only seems to affect mysqldump! BTW, once it helped me to solve such a very-very similar problem by only adding -q to the mysqldump commandline. God knows why was all the database buffered in stdout, but mysqldump swallowed more than 800mb of ram on a huge table (was dumping udmsearch database) while the box had only 768mb ram. -q helped. -- For technical support contracts, goto https://order.mysql.com/ This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
