I put it in both....
----- Original Message -----
From: "Mikhail Berman" <mberman@stripped>
To: "Melissa Dougherty" <melissa@stripped>; <dpgirago@stripped>
Cc: <win32@stripped>
Sent: Thursday, September 14, 2006 4:09 PM
Subject: RE: MySQLDump
In my.cnf there are two sections where max_allowed_packet value can be
set.
One in [mysql] and one in [mysqldump]
Please check where you setting your value, you need [mysqldump] section.
Hoping this helps
Mikhail Berman
-----Original Message-----
From: Melissa Dougherty [mailto:melissa@stripped]
Sent: Thursday, September 14, 2006 3:48 PM
To: dpgirago@stripped
Cc: win32@stripped
Subject: Re: MySQLDump
I increased the limit to 1gb... but got the same error. Do you think if
I turned on the general query log it would give anymore info?
Melissa
----- Original Message -----
From: <dpgirago@stripped>
To: "Melissa Dougherty" <melissa@stripped>
Cc: <win32@stripped>
Sent: Thursday, September 14, 2006 2:57 PM
Subject: Re: MySQLDump
>
>> I increased the max_allowed_packet variable to 72m from 64m and also
> upped
>> the connect_timeout. But the dump still error the same way.
>>
>> Melissa
>
> The manual says:
>
> The protocol limits for max_allowed_packet is 16M in MySQL 3.23
and
> 1G in MySQL 4.0.
>
> Perhaps I've not been following this thread closely enough, but why
not
> make it a gigabyte, just as a test??
>
> -- David
>
>
>
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe:
http://lists.mysql.com/win32?unsub=1
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=1
