Right, I read the manual, and I'm trying to wonder what that really means? However, I ran mysql_upgrade, for a few seconds, and then got a couple of tables as needing repair, so I checked their SQL creation, and none of them had TEXT indexes, but did have a TEXT column. How do we know what the CHECK saw as bad in the table? Rather, can we?
On Feb 16, 2008 9:24 PM, Paul DuBois <[EMAIL PROTECTED]> wrote: > At 9:12 PM -0600 2/16/08, Hayden Livingston wrote: > >Ahh yes, but I canceled it before all the tables/databases were > >checked. But I guess, you're saying, it'll "work" but, I might get bad > >results. How when you mean certain queries, is there like some type? > >scans? or the ones that key off that index? or a subset of them? > > By "certain queries," I mean that I don't know how to predict > which queries might not work correctly. :-) I'll wimp out and > quote the manual: > > http://dev.mysql.com/doc/refman/5.0/en/upgrading-from-4-1.html > > "Incompatible change: The indexing order for end-space in TEXT > columns for InnoDB and MyISAM tables has changed. Starting from > 5.0.3, TEXT indexes are compared as space-padded at the end (just as > MySQL sorts CHAR, VARCHAR and TEXT fields). If you have a index on a > TEXT column, you should run CHECK TABLE on it. If the check reports > errors, rebuild the indexes: Dump and reload the table if it is an > InnoDB table, or run OPTIMIZE TABLE or REPAIR TABLE if it is a MyISAM > table." > > So if CHECK TABLE doesn't complain, you should be okay. > > > > > > >Thanks! > > > >On Feb 16, 2008 9:09 PM, Paul DuBois <[EMAIL PROTECTED]> wrote: > >> At 9:01 PM -0600 2/16/08, Hayden Livingston wrote: > >> >We're trying to upgrade from 4.1.20 to 5.0.54. The problem is running > >> >mysql_upgrade. It's turning out to be that about 70% of our tables > >> >(over 800GB) are being needing repair. > >> > > >> >The question is, will it be possible to "get by" without upgrading? > >> >Eventually we'll get to it, but will data be served from these tables > >> >if we don't? A lot of our tables DO have TEXT indexes, which > >> >apparently have gone under some padding related incompatible changes, > >> >what does this really mean, these tables can't be read or they will be > >> >inefficient? > >> > >> The server should be able to read them (if it couldn't, mysql_upgrade, > >> which uses mysqlcheck, a client, couldn't tell the server to repair > >> them!). But until those TEXT indexes are rebuilt, you might get > > > incorrect results for some queries. > > -- > Paul DuBois, MySQL Documentation Team > Madison, Wisconsin, USA > MySQL AB, www.mysql.com > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
