Opening Database Crashes Mysql

[Jacques Philip]

Opening database crashes MySql when some views have invalid fields or tables.

MySql logs indicate the crash happens when MySql tries to create a temporary table for the view.

This does not happen in MySql administrator which indicates the view is invalid instead.

Maybe more error checking would be needed when trying to list the views.

[peterlaursen]

If the MySQL server crashes is is a bug in the MySQL server and not in SQLyog.

You should report such here: http://bugs.mysql.com

Or do you mean that SQLyog crashes? And what does it meant that “some views have invalid fields or tables”?

[Jacques Philip]

'peterlaursen' wrote:

If the MySQL server crashes is is a bug in the MySQL server and not in SQLyog.

You should report such here: http://bugs.mysql.com

There is nothing wrong with MySql, when I list the views with MySql Administrator, it tells me which views are invalid and does not try to create a temporary table for those views.

Quote:

Or do you mean that SQLyog crashes? And what does it meant that “some views have invalid fields or tables”?

MySql crashes means it stops and does not restart. It can be restarted manually though and runs fine as long as we do not try to list the database objects with Sqlyog.

The last thing it does reported in the log is that it tries to create a temporary table for a view that uses tables that have been deleted from the database. Again, this does not happen with MySql administrator and I believe it does not necessarily cause a crash with Sqlyog as I had invalid views in the past that did not cause problem. (It may be that the missing table have to be part of a certain type of join to cause a crash).

I am not sure if the code you have to list the views in Sqlyog allows you to verify that they use valid objects or if you can prevent MySql from creating a temporary table for the view at that point, looking at the source code of MySql administrator may help.

We fixed our problem by correcting or deleting the invalid views, but never the less, I think Sqlyog should have more error checking and report the views that are invalid instead of doing something resulting in creating a temporary table involving non existing objects.

[peterlaursen]

It does not matter!  If the server crashes it is a server bug – simply!  SQLyog simply sends SQL statements to the server – that is all because that is all what a client can do.  A reference to another cleint ('MySQL Administrator' that is discontinued BTW) is also completely irrelevant.  A server crash is a server crash.  An the bug is inside the program that crashes.  The server crashes adn the bug is a server bug. (and of course it will create a temporary table. A VIEW is alway a temporary table in MySQL as MySQL does not have 'materialized views')

No action will be taken on our side. I suggest you try to upgrade your server in order to see if this will solve the server crash. What is your server version BTW?

[peterlaursen]

There is a similar report here http://bugs.mysql.com/bug.php?id=5151 (it is with a very early 5.0 server and fixed 5+ years ago in the server code).

Please also read this FAQ:

http://www.webyog.com/faq/content/1/178/en/sqlyog-is-a-client-for-the-mysql-server-_-but-what-server-versions-are-supported.html

[Jacques Philip]

'peterlaursen' wrote:

There is a similar report here http://bugs.mysql.com/bug.php?id=5151 (it is with a very early 5.0 server and fixed 5+ years ago in the server code).

Please also read this FAQ:

http://www.webyog.com/faq/content/1/178/en/sqlyog-is-a-client-for-the-mysql-server-_-but-what-server-versions-are-supported.html

As I said, I fixed my problem by fixing the views, I just mentioned this to you because I thought it would be a good feature of Sqlyog to report when views reference objects that do not exist so that I can fix those, but if you do not think so, fine with me.

It does not matter if it crashes the server or not, it would just be a nice feature.

[peterlaursen]

As said: we will not waste our time 'working around' bugs in old server versions.  I believe recent servers will not crash but report an error. We return that error to the user. Since the error is on the server (ie. broken VIEWs not handled properly by the server) the server will have to handle it.  If (the now discontinued and completely dead) MA program had a 'dirty client-side work around' for a server bug in early 5.0 servers it is not our problem, and does not inspire or oblige us at all.  

What is your server version?  Execute “SELECT VERSION();” to find out the exact version. Without that information this discussion is completely silly.

[Author]

Posts