Cookies op Tweakers

Tweakers maakt gebruik van cookies, onder andere om de website te analyseren, het gebruiksgemak te vergroten en advertenties te tonen. Door gebruik te maken van deze website, of door op 'Ga verder' te klikken, geef je toestemming voor het gebruik van cookies. Wil je meer informatie over cookies en hoe ze worden gebruikt, bekijk dan ons cookiebeleid.

Meer informatie

Door , , 5 reacties
Bron: MySQL AB

MySQL AB heeft zojuist een pre-release van MySQL 3.23.50 uitgebracht. De nieuwe versie kent een aantal bugfixes en er werden nieuwe features aan de InnoDB engine toegevoegd. De belangrijkse is volwaardige ondersteuning van foreign key constraints door de InnoDB table handler. InnoDB beschikt al enige tijd over foreign keys, echter zonder expliciete ondersteuning door MySQL. Daardoor verdwenen de foreign key constraints bij het uitvoeren van een ALTER TABLE of CREATE INDEX en werden ze vergeten door mysqldump, met als resultaat dat de foreign keys feitelijk onbruikbaar waren. Deze problemen zijn in deze release opgelost. Verder is er nu ook support voor ON DELETE CASCADE.

De 3.23.50 Linux x86 binaries zijn gecompileerd met een nieuwe glib library en een andere gcc compiler (3.0.4). MySQL AB heeft daarom besloten eerst een pre-release uit te brengen alvorens MySQL 3.23.50 stabiel te verklaren. Het is dus niet aan te raden om de pre-release te gebruiken op productie servers. Uit eigen ervaring kunnen we zeggen dat de laatste 3.23.49a stable release bijzonder stabiel presteert. De Tweakers.net databaseservers hebben inmiddels een MySQL uptime van 42 tot meer dan 50 dagen. Artemis heeft sinds de laatste reboot bijna 900 miljoen queries verwerkt zonder een herstart van de MySQL daemon . Hieronder de informatie uit de MySQL mailinglist en de changelogs:

Hi!

3.23.50 is basicly just a bug fix release compare do 3.23.49a. There is however two things one should be aware of regarding 3.23.50 (both only affecting our Linux x86 binaries (normal and RPM's):

  • We have switched to a new updated glib library, because we found a critical memory corruption bug (introduced by us) in the old glibc library that we used to compile 3.23.49. (older MySQL binaries are not affected by this problem)
  • We have changed compiler to gcc 3.0.4 (because the old gcc compiler we used couldn't compile with an alternative glibc library).
As 3.23 is a stable release version, we don't want to release 3.23.50 to the general public right away, as we want to be sure that the new gcc version works in practice as good as it has worked on our internal machines. You can now find 3.23.50 at the following link: http://www.mysql.com/downloads/mysql-3.23-pre.html

If we don't get any fatal bug reports by the end of the week for this version, we will then move it to our standard download page. If you find anything wrong/strange with this release compared to older 3.23 releases, please send a full bug report to bugs@lists.mysql.com and we will fix it ASAP!

* MySQL 3.23.50 changelog:

  • Fixed problem with `crash-me' and gcc 3.0.4.
  • Fixed that `@@unknown_variable' doesn't hang server.
  • Added `@@VERSION' as a synonym for `VERSION()'.
  • `SHOW VARIABLES LIKE 'xxx'' is now case insensitive.
  • Fixed timeout for `GET_LOCK()' on HPUX with DCE threads.
  • Fixed memory allocation bug in the glibc library used to build Linux binaries, which caused mysqld to die in 'free()'.
  • Fixed `SIGINT' and `SIGQUIT' problems in `mysql'.
  • Fixed bug in character table converts when used with big ( > 64K) strings.
  • `InnoDB' now retains foreign key constraints through `ALTER TABLE' and `CREATE/DROP INDEX'.
  • `InnoDB' now allows foreign key constraints to be added through the `ALTER TABLE' syntax.
  • `InnoDB' tables can now be set to automatically grow in size (autoextend).
  • Fixed some buffer overflow problems when reading startup parameters.
  • Because of problems on shutdown we have now disabled named pipes on windows by default. One can enable named pipes by starting mysqld with `--enable-named-pipe'.
  • Fixed bug when using `WHERE key_column = 'J' or key_column='j''.
  • Fixed core-dump bug when using `--log-bin' with `LOAD DATA INFILE' without an active database.
  • Fixed bug in `RENAME TABLE' when used with `lower_case_table_names=1' (default on Windows).
  • Fixed unlikely core-dump bug when using `DROP TABLE' on a table that was in use by a thread that also used queries on only temporary tables.
  • Fixed problem with `SHOW CREATE TABLE' and `PRIMARY KEY' when using 32 indexes.
  • Fixed that one can use `SET PASSWORD' for the anonymous user.
  • Fixed core-dump bug when reading client groups from option files using `mysql_options()'.
  • Memory leak (16 bytes per every *corrupted* table) closed.
  • Fixed binary builds to use `--enable-local-infile'.
  • Update source to work with new `bison' version.
  • Updated shell scripts to new agree with new POSIX standard.
  • Fixed bug where `DATE_FORMAT()' returned empty string when used with `GROUP BY'.
* InnoDB 3.23.50 changelog:
  • InnoDB now supports an auto-extending last data file. You do not need to preallocate the whole data file at the database startup.
  • Made several changes to facilitate the use of the InnoDB Hot Backup tool. It is a separate non-free tool you can use to take online backups of your database without shutting down the server or setting any locks.
  • If you want to run the InnoDB Hot Backup tool on an auto-extending data file you have to upgrade it to version ibbackup-0.35.
  • The log scan phase in crash recovery will now run much faster.
  • Starting from this server version, the hot backup tool truncates unused ends in the backup InnoDB data files.
  • To allow the hot backup tool to work, on Windows we no longer use unbuffered i/o or native async i/o; instead we use the same simulated async i/o as on Unix.
  • You can now define the ON DELETE CASCADE or ON DELETE SET NULL clause on foreign keys.
  • FOREIGN KEY constraints now survive ALTER TABLE and CREATE INDEX.
  • We suppress the FOREIGN KEY check if any of the column values in the foreign key or referenced key to be checked is the SQL NULL. This is compatible with Oracle, for example.
  • SHOW CREATE TABLE now lists also foreign key constraints. Also mysqldump no longer forgets about foreign keys in table definitions.
  • You can now add a new foreign key constraint with ALTER TABLE ... ADD CONSTRAINT FOREIGN KEY (...) REFERENCES ... (...).
  • FOREIGN KEY definitions now allow backquotes around table and column names.
  • MySQL command SET TRANSACTION ISOLATION LEVEL ... has now the following effect on InnoDB tables: if a transaction is defined as SERIALIZABLE then InnoDB conceptually adds LOCK IN SHARE MODE to all consistent reads. If a transaction is defined to have any other isolation level, then InnoDB obeys its default locking strategy which is REPEATABLE READ.
  • SHOW TABLE STATUS no longer sets an x-lock at the end of an auto-increment index if the auto-increment counter has already been initialized. This removes in almost all cases the surprising deadlocks caused by SHOW TABLE STATUS.
  • Fixed a bug: in a CREATE TABLE statement the string 'foreign' followed by a non-space character confused the FOREIGN KEY parser and caused table creation to fail with errno 150.

Lees meer over

Versienummer:3.23.50
Besturingssystemen:Windows 9x, Windows NT, Windows 2000, Linux, BSD, Windows XP, macOS, OS/2, Solaris, UNIX
Website:MySQL AB
Download:http://www.mysql.com/downloads/mysql-3.23-pre.html
Moderatie-faq Wijzig weergave

Reacties (5)

4.0.1-2 staat ook al een hele tijd op de site. Zal ook niet stable zijn...maar wat doet dat dan?
Dat is de alpha van MySQL 4.0. Op dit moment zijn ze al erg lang bezig met 4.0.2. Gezien het grote aantal bugfixes lijkt het erop dat ze 4.0 beta gaan verklaren en daarna gaan beginnen met 4.1 waar de grote veranderingen in komen (stored procedures enzo).
Dat klopt
MySQL 4.1, the following development release

Internally, through a new .frm file format for table definitions, MySQL 4.0 lays the foundation for the new features of MySQL 4.1, such as nested subqueries, stored procedures, and foreign key integrity rules, which form the top of the wish list for many of our customers. Along with those, we will also include simpler additions, such as multi-table UPDATE statements.
Ik gebruik nu 4.01-alpha op mn servertje, geen enkel probleem mee. Als ik nu naar 3.23.50 zou willen, krijg ik dan ook problemen met mn InnoDB tables?
MySQL 3.23.50 gebruikt een nieuwere InnoDB versie als 4.0.1, dus 'downgraden' lijkt me geen probleem. Je kunt ook wachten op 4.0.2, het is alleen niet duidelijk wanneer die versie uit moet komen ("when it's done").

Op dit item kan niet meer gereageerd worden.



Apple iOS 10 Google Pixel Apple iPhone 7 Sony PlayStation VR AMD Radeon RX 480 4GB Battlefield 1 Google Android Nougat Watch Dogs 2

© 1998 - 2016 de Persgroep Online Services B.V. Tweakers vormt samen met o.a. Autotrack en Carsom.nl de Persgroep Online Services B.V. Hosting door True