Baseball Toaster was unplugged on February 4, 2009.
Update 2:: Still had some trouble getting the site up, and then I had to leave because my daughter was getting five teeth pulled. Sorry, she takes priority over y'all.
So I restarted the server, but I may have to bounce it a couple more times before it's running smoothly again.
Update: No sooner did I post the following than our ISP shut down our server, for some reason. So we were down for five hours over night because of my stuff, then we were down an additional three hours because of our ISP. ISP says it was a "kernel failure". OK, whatever...
I also got a (bogus) $250 parking ticket from an AC Transit cop yesterday. If the A's hadn't won last night, I'm not sure how many things there'd be around my house that weren't smashed.
Original post:
Well, the upgrade took me a heck of a lot longer than I thought it would. One of these days, I'm gonna pay for a development environment that's identical to the production one, so I can figure these problems out before it affects y'all. Perhaps after we get some revenues coming in...
I was trying to do two things:
Seems that you can't just drop an index in MySql and forget about it. MySql then wants to rebuild all the indexes on that table. That took a while, about 10 minutes per index.
Then when I upgraded the Apache server, mod_perl wasn't happy anymore. So I had to recompile it, and reinstall it, and that broke some code. So I had to fix the code to work with the new version of mod_perl.
Then when all that was over, it seems that I needed one of those dropped indexes after all, because the site was slower than ever. So I had to figure out which of those indexes I dropped was the one I still needed with some step-by-step debugging. So I had to recreate that index again, which meant rebuilding all the indexes on that table, which again took time.
I finally got the site working at about 4:30am. But then it seemed a little unstable, so I backed out the threaded version, and went back to the non-threaded server, because I need some sleep.
So if the site seems slow or has a bug or two, I'll fix it when I wake up. Perhaps I should set my alarm for the A's game at 12:35...
Anyway, thanks for your patience...
I work on Oracle and MySQL in my day-job and the only thing I kinda like about MySQL is the readline support in the command line client. I've heard good things about PostgreSQL, but I've only played around with it a little. Once you've grasped Multiversion Concurrency Control, it's hard to use anything else.
If you're using DBI (right? RIGHT??!!?) it should be easy to convert, if you're interested. If you need any pointers/tips/etc I'd be happy to help. My PG is good, my perl not so much.
But even though MySQL hasn't been a professional quality DB in the past, it's getting there. I like and I'm impressed with the direction it's heading, and the speed at which it's traveling. It looks to me like it's gonna win in the long run, so that's why I went with it. I've been on the losing side in far too many database wars in my career.
Postgres has its quirks, too. All aggregrates do full table scans, for example.
The way I've coded it, I can switch between DBs fairly easily; I just have to copy a separate query file for the new database, and adjust any queries that might have different syntax.
Comment status: comments have been closed. Baseball Toaster is now out of business.