高橋(智)です。

Shin-ichi Tsurunaga wrote:
> 
> 鶴長です。
> オフ会にご参加の皆様無事帰れましたでしょうか？　まだこの時間だと

  大変有意義な集まりでした。幹事の鶴長様、ありがとうございました。

  皆さんあまり MySQL-Max(MySQL/InnoDB)を使ってらっしゃらないように
感じました。
  とあるシステム(Linux & Java & CORBA)で数十GBのInnoDBデータベース
を作成しましたが何ら支障無く動作します。デフォルトのページサイズ16KB
などの制限値から計算した最大サイズ約64GBまではさすがに試してませんが、
快適に使えます。(※ページサイズを64KBに変更してコンパイルし直せば、
最高約256GBまで行けるハズ)

  つい最近リリースされた3.23.48では、正式にInnoDBがstableな状態に
なるだろうとアナウンスされたようですし、こんないいモノを使わない
のはたいへん勿体無いことだと思います。

  ご参考までに、本家(外国)のMySQLメーリングリストで流れた内容を以下
に引用します。
------------ ここから引用 ------------------------------------------
Subject: MySQL/InnoDB-3.23.48 is released

Hi!

InnoDB is a MySQL table type which adds transactions, row level locking, and
foreign key constraints to MySQL.

InnoDB is included in the MySQL-Max-3.23.48, MySQL-4.0, and MySQL-Max-4.0
distributions of MySQL. These can be downloaded from http://www.mysql.com.
For more information about InnoDB see the online refererence manual at
http://www.innodb.com/ibman.html.

InnoDB version 3.23.48 contains some small improvements, and several bug
fixes. Since the bug in SHOW CREATE TABLE could cause memory corruption and
random crashes, especially in mysqldump, I recommend that InnoDB users
upgrade to 3.23.48.

The version 3.23.48 will be the first MySQL/InnoDB version which is
officially declared as stable by Innobase Oy, unless some serious bug is
reported from it.
.....
MySQL/InnoDB-3.23.48 changelog February 9, 2002:

* Tuned the SQL optimizer to favor more often index searches over table
scans.

* Fixed a performance problem when several large SELECT queries are run
concurrently on a multiprocessor Linux computer. Large CPU-bound SELECT
queries will now also generally run faster on all platforms.

* If MySQL binlogging is used, InnoDB now prints after crash recovery the
latest MySQL binlog name and the offset InnoDB was able to recover to. This
is useful, for example, when resynchronizing a master and a slave database
in replication.

* Added better error messages to help in installation problems.

* One can now recover also MySQL temporary tables which have become orphaned
inside the InnoDB tablespace.

* InnoDB now prevents a FOREIGN KEY declaration where the signedness is not
the same in the referencing and referenced integer columns.

* Fixed a bug: calling SHOW CREATE TABLE or SHOW TABLE STATUS could cause
memory corruption and make mysqld to crash. Especially at risk was
mysqldump, because it calls frequently SHOW CREATE TABLE.

* Fixed a bug: if on Unix you did an ALTER TABLE to an InnoDB table and
simultaneously did queries to it, mysqld could crash with an assertion
failure in row0row.c, line 474.

* Fixed a bug: if inserts to several tables containing an auto-inc column
were wrapped inside one LOCK TABLES, InnoDB asserted in lock0lock.c.

* In 3.23.47 we allowed several NULLS in a UNIQUE secondary index. But CHECK
TABLE was not relaxed: it reports the table as corrupt. CHECK TABLE no
longer complains in this situation.

* Fixed a bug: on big-endian processors like Sparc SHOW VARIABLES showed
boolean-values InnoDB startup parameters always off though they were
switched on.
.....

There is one known bug which was not yet fixed in 3.23.48. InnoDB foreign
key constraints cannot be declared if you specify a non-latin1 character set
as the default character set in my.cnf. A source code patch to this is
available at http://www.innodb.com/foreign.txt.

In the MySQL layer of code there were also some minor bug fixes. Please
consult the MySQL-3.23.48 release note about those.

Best regards,

Heikki Tuuri
Innobase Oy
------------ ここまで引用 ------------------------------------------

-- 
高橋智宏
  Java読書会( http://www.t3-jpn.com/bof/ )
  T3-Japan( http://www.t3-jpn.com/ )