Hello.
See:
http://dev.mysql.com/doc/refman/5.0/en/gone-away.html
Tripp Bishop wrote:
> Howdy all,
>
> First off, We're running 5.0.15.
>
> Theres a particular update statement that we run that
> updates data in several tables. On our mac OSX test
> server (also running 5.0.15) th
On 1/4/06, Tripp Bishop <[EMAIL PROTECTED]> wrote:
>
> We did recently upgrade the server from 4.0.40 to
> 5.0.15 and we did not dump the tables and reimport
> them. On the MAC we did do a dump and reimport. I
> wonder if that could be the cause of this problem. I
> had forgetten about that importa
The fact that on your Mac installation you re-imported your table data
makes me think it's an index efficiency issue. I have seen MySQL just
lose the connection if the join becomes massively big. On re-import,
the indexes would have been rebuilt and your query would be able to
take advantage of the
l Message-
> From: Tripp Bishop [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 04, 2006 11:01 AM
> To: emierzwa; mysql@lists.mysql.com
> Subject: RE: Lost Connection executing query
>
> The query fails instantly so I don't think it's a
> timeout issue.
>
&
ubject: RE: Lost Connection executing query
The query fails instantly so I don't think it's a
timeout issue.
The wait_timeout and interactive_timeout variables are
set to 28800.
The server seems to be crashing and auto restarting
because as you suggested the uptime is small when I do
heck section "A.2.8. MySQL server has gone
> away" in the online
> manual, which also covers your message, for list of
> things to try.
>
http://dev.mysql.com/doc/refman/5.0/en/gone-away.html
>
> Ed
> -Original Message-
> From: Tripp Bishop [mailto:[
v.mysql.com/doc/refman/5.0/en/gone-away.html
Ed
-Original Message-
From: Tripp Bishop [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 03, 2006 4:45 PM
To: mysql@lists.mysql.com
Subject: Lost Connection executing query
Howdy all,
First off, We're running 5.0.15.
Theres a particular upda
Howdy all,
First off, We're running 5.0.15.
Theres a particular update statement that we run that
updates data in several tables. On our mac OSX test
server (also running 5.0.15) the query executes
quickly and without any errors or warnings.
On our linux box, which is our production box, we get
