From: shane <sh...@lo...> - 2003-06-12 22:24:12
|
I'm venturing to upgrade my slashsites to use mysql4. I took my test box (that's a direct clone of the production server), backed up the /usr/local/var mysql data files, uninstalled mysql3 (it was from src) and installed the latest stable mysql4 binary (krow had recommended numerous times on irc to use the rpm, or binary, not the src). Then I pulled from backups two site db's from the production site, and put them into /usr/local/mysql/data. Fired up mysql4 and all looks good - could read and write to the tables in both slashdb through the mysql client. (for the curious, this is on redhat 7.1 boxes) In a few minutes I'll run install-slashsite and see what happens. Anyway, here's what I'm wondering. If this works, I'll do a very similar process on the production box after throughly testing everything. At that point, do I: 1) need to do anything to convert the tables at all to a newer type? need may be a bit of a stretch... should I? I recall reading something about a newer table type that could be better somewhere. Maybe I'm thinking of something else, I don't know. But I thought I'd ask. 2) The sites are current cvs as of this morning am when I updated them. Do I need to go back through the sql/upgrades file and find all the points where it states something like "if you are running mysql3 do this and if you're running mysql4 do that" and implement/rework the mysql4 lines so as to apply to the slashdb's under mysql4? Thanks, Shane |
From: Brian A. <br...@ta...> - 2003-06-12 22:40:46
|
On Thu, 2003-06-12 at 15:21, shane wrote: > 1) need to do anything to convert the tables at all to a newer type? need may > be a bit of a stretch... should I? I recall reading something about a newer > table type that could be better somewhere. Maybe I'm thinking of something > else, I don't know. But I thought I'd ask. If you are upgrading from a very old version of MySQL, make sure your tables are MyISAM. Also, you will want to rebuild all of the fulltext indexes (look in the dump file for the Search plugin to see which indexes are fulltext). -Brian -- _______________________________________________________ Brian "Krow" Aker, br...@ta... Slashdot Senior Developer Seattle, Washington http://krow.net/ http://askbrian.org/ _______________________________________________________ You can't grep a dead tree. |
From: Randall H. <li...@so...> - 2003-06-12 23:17:28
|
Thus spoke shane <sh...@lo...> ( Thu, 12 Jun 2003 18:21:46 -0400 ): > I'm venturing to upgrade my slashsites to use mysql4. FYIW, I've been running two testing sites (R_2_3_0_62) on MySQL 4.0.13 for a few weeks and they've been fine. Randall |
From: Matt C. <ma...@op...> - 2003-06-13 13:19:13
|
Hi, Shane. I've also been experimenting with MySQL 4 on a test machine, and am hoping to try it on a production box soon. In case anyone's interested, the debian stable distribution still uses 3.23, but I found debian packages on www.apt-get.org that work nicely. Overall, I find it's a big improvement (many options are now configurable at run time which were previously only available at compile time, and the query caching is great). On Thu, Jun 12, 2003 at 06:21:46PM -0400, shane wrote: >1) need to do anything to convert the tables at all to a newer type? >need may be a bit of a stretch... should I? I recall reading something >about a newer table type that could be better somewhere. As Krow says, you need to rebuild your fulltext indices to take advantage of new MySQL 4 features. The new table format you're thinking of is probably MyISAM, which was already around in 3.23. The slash schema already uses this table type, so you don't need to worry about that. I'd suggest you read the full documentation on upgrading from 3.23 to 4.0, however, which you can find here: http://www.mysql.com/downloads/mysql-4.0.html That covers rebuilding the tables, and other issues. -- matt -- Openflows Networks Ltd. New York | Toronto | Waterloo | Vienna http://openflows.org People are intelligent. Machines are tools. |
From: George C. <ga...@sp...> - 2003-06-22 15:38:31
|
** Reply to message from shane <sh...@lo...> on Thu, 12 Jun 2003 18:21:46 -0400 Hi all, In prep for the latest slashcode tags, I want to upgrade to mysql 4. My test system (my laptop) can't readily make the jump. Too old with too many RPM dependencies. It appeared that I'd have to update 100s of RPMs. It's a really old SuSE installation. Production is Debian (Knoppix). On another system I was able to pretty easily do an apt-get upgrade to the mysql 4.x packages, and everything looks clean, but slash isn't installed there, and it is yet a different version of Debian from production. At these reasonably current releases, should it really be as simple as running the apt-get upgrade? Any traps I should be aware of? Any other suggestions? (I know... I really ought to match a test system to my production system <g>) Also, at tag _97, there was a recommendation to stay with _96. Have the issues been resolved and is _100 looking okay? Production system is mysql Ver 11.18 Distrib 3.23.52, for pc-linux-gnu (i686) perl, v5.8.0 built for i386-linux-thread-multi slash T_2_3_0_82 Thanks, George |
From: Jamie M. <ja...@mc...> - 2003-06-22 19:43:02
|
I can't help you with your RH issues, but my three test sites are all on Debian testing, and I'm using the mysql that apt-get fed me, with no problems. It's "mysqld Ver 4.0.13 for pc-linux-gnu on i686". > Also, at tag _97, there was a recommendation to stay with > _96. Have the issues been resolved and is _100 looking okay? Yes. As the INSTALL file (now) says, T_* tags are always "living on the edge," and the R_* tags are merely "near the edge". And yes, we know we haven't issued a new R_* tag for a while -- once we get a nice clean stable solid version, we will, but it's been a few months now since we were totally happy. But if you're happy on the edge, any recent T_* tag is better than _97. |
From: shane <sh...@lo...> - 2003-06-23 10:20:54
|
On Sunday 22 June 2003 11:37, George Clark wrote: > ** Reply to message from shane <sh...@lo...> on Thu, 12 Jun 2003 > 18:21:46 -0400 > > Hi all, > > In prep for the latest slashcode tags, I want to upgrade to mysql 4. >[...] > At these reasonably current releases, should it really be as simple as > running the apt-get upgrade? Any traps I should be aware of? Any other > suggestions? (I know... I really ought to match a test system to my > production system <g>) I was working on doing this a few weeks ago. I have 2 identical boxes, one's the production website, one's the dev website. mysql 3.x was installed from source. I shutdown apache, slashd, mysql, and other misc software on the dev box. Then installed the binary of mysql4 (these are redhat machines. Krow had recommended using either binary or rpm, but *not* src to install). Anyway, after upgrading, I grabbed Slash's latest CVS, installed. It didn't work. I had to update some modules from CPAN. So I did that. Ran install-slashsite, made a new site. Took a db backup from the previous evening from a production website, restored to this site's new db. Changed hostname/etc info in db. Fired up slashd & httpd. No problems what-so-ever. The only thing that was recommended to me was to rebuild the full text indexes, which I've unfortunately been too busy to do. if anyone's done this, if you have the sql handy to do it, can you share it with us all? If not, after I get around to doing it I'll post it somewhere. Shane |
From: shane <sh...@lo...> - 2003-07-08 00:58:02
|
On Monday 23 June 2003 06:18, shane wrote: > On Sunday 22 June 2003 11:37, George Clark wrote: > > ** Reply to message from shane <sh...@lo...> on Thu, 12 Jun 2003 > > 18:21:46 -0400 > > > > Hi all, > > > > In prep for the latest slashcode tags, I want to upgrade to mysql 4. > >[...] >[...] > > The only thing that was recommended to me was to rebuild the full text > indexes, which I've unfortunately been too busy to do. if anyone's done > this, if you have the sql handy to do it, can you share it with us all? If > not, after I get around to doing it I'll post it somewhere. as promised, I think this will rebuild all the full text's on a current slashcvs site: REPAIR TABLE stories QUICK; REPAIR TABLE story_text QUICK; REPAIR TABLE comments QUICK; REPAIR TABLE comment_text QUICK; REPAIR TABLE users QUICK; REPAIR TABLE pollquestions QUICK; REPAIR TABLE journals QUICK; REPAIR TABLE journals_text QUICK; REPAIR TABLE submissions QUICK; Shane |