MySQL 3.23.48 released

[TommyBALL]

Just got this message from the MySQL announce-list...MySQL 3.23.48 is now released

This version fixes some small bugs, and for most people there should
not be any big reason to upgrade.

Changes in release 3.23.48
--------------------------

* Changed to use `autoconf' 2.52 (from `autoconf' 2.13)

* Fixed bug in complicated join with `const' tables.

* Added internal safety checks for InnoDB.

* Some InnoDB variables was always shown in `SHOW VARIABLES' as
`OFF' on high-byte-first systems (like sparc).

* Fixed problem with one thread using an InnoDB table and another
thread doing an `ALTER TABLE' on the same table.

* If inserts to several tables containing an auto-inc column are
wrapped inside one `LOCK TABLES', InnoDB asserted in `lock0lock.c'.

* `SHOW GRANTS' now shows `REFERENCES' instead of `REFERENCE'.

Regards,
MontyDownload here...
http://www.mysql.com/downloads/mysql-3.23.html

As usual the Win32 release will follow in a week or so...

Regards
- Tommy

[Chris Schreiber]

Nothing exciting (unless you use InnoDB), but thanks :)

[ethank]

Can't use InnoDB with VBulletin anyhow without doing some heavy mods.... :(

Ethan

[doofoo]

hmm.. We're actually using INNODB with our board without any problems. It didn't take anytime at all to convert it. However, we are still having problems where our slow queries will start to go crazy. We even upgraded to the most recent version of mysql. We cannot find out what it's based off of, but it seems like every 30 minutes or so during peak load the threads go up and slow queries go up.

We're going to try downgrading to 2.2.1, because most of the problems came after we upgraded to 2.2.2 (Yes, we have the new forumdisplay) But it only helps a little bit. not a lot.

-Mike

[ethank]

Originally posted by doofoo
hmm.. We're actually using INNODB with our board without any problems. It didn't take anytime at all to convert it. However, we are still having problems where our slow queries will start to go crazy. We even upgraded to the most recent version of mysql. We cannot find out what it's based off of, but it seems like every 30 minutes or so during peak load the threads go up and slow queries go up.

We're going to try downgrading to 2.2.1, because most of the problems came after we upgraded to 2.2.2 (Yes, we have the new forumdisplay) But it only helps a little bit. not a lot.

-Mike

Its the select count(*) that casues the slow queries. On a board with a few hundred thousand posts, it makes InnoDB unusable. MyISAM tables cache the row count outside the table itself, so it doesn't count implicitly on each select count(*) request.

InnoDB does not, you'd have to program it in.

EThan

[doofoo]

If we left the counting in a myisam table, wouldn't it still have locking problems to keep count?

Thanks,
mike

[ethank]

Originally posted by doofoo
If we left the counting in a myisam table, wouldn't it still have locking problems to keep count?

Thanks,
mike

No, you'd have to redo the DB_site class a bit so that counts are taken and tracked in a seperate table. Or redo how vBulletin gets counts. Its only a handful of queries I think. Outside of this issue, InnoDB would be nice.

[doofoo]

I looked in your profile and found you aim handle. Are you ever on? It would be a little easier to get ahold of you. I would greatly appreciate any help, we are trying to get this resolved. We have been having problems for the past few weeks and could really use a little help in getting this converted.

btw, my aim name is doofoo

Thanks Alot,
Mike

[ethank]

Originally posted by doofoo
I looked in your profile and found you aim handle. Are you ever on? It would be a little easier to get ahold of you. I would greatly appreciate any help, we are trying to get this resolved. We have been having problems for the past few weeks and could really use a little help in getting this converted.

btw, my aim name is doofoo

Thanks Alot,
Mike

I'm usually on, but today I'm busy with something (see Hollywood thread elsewhere in CHit Chat if you care to know what :))

I'll be on all day tomorrow though and we can step through some of the code. I have horror stories! You can also find the thread about my attempt at switching to InnoDB within this forum if you search for it.

Ethan