Hello.
I've never heard that big values of max_allowed_packed had produced problems. So usually putting it to big enough values shouldn't break anything in most cases. Please, next time send a copy of your message to the list, more experienced users can give a good advice. >we are replicating some text columns (though they are a comparitievly >small % of our DML volume). > >that thought had crossed my mind (Oracle used to blame the ORA-00600s >AQ kept coughing up on CLOBs). I guess it's certainly possible we had >a "high water" text value come through yesterday. > >so does the max_allowed_packet need to be big enough to accomodate a >row, a DML statement or a transaction (they're in innodb tables)? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
