Hello.
Maybe. Use --skip-extended-insert in this case. Sid Lane <[EMAIL PROTECTED]> wrote: > I think I've foind the culprit: > > a problem (logical, not physical) had been discovered with a couple of > tables which were fixed by truncating them in the production > replication master and reloading them from a mysqldump of the > corrected tables from the qc/dev database. the dump was done w/the -e > (which makes sense) flag hence REALLY BIG individual insert statements > even though the table itself wasn't that big nor were any individual > rows. > > does this sound plausible? > -- 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]
