Log in

No account? Create an account

5.1, Innodb Plugin Release

« previous entry | next entry »
Dec. 3rd, 2008 | 03:56 pm

In MySQL 5.1 related new, Innodb has announced the release of their Innodb Plugin Engine for MySQL.

So why do I blog about it?

Because the Innodb plugin engine is the default engine Drizzle :)

Monty Taylor finished up the work last night to import it into Drizzle, and I just finished my review of the engine and have pushed it into our main branch.

Some of the advantages:

  • Fast index creation: add or drop indexes without copying the data
  • Data compression: shrink tables, to significantly reduce storage and i/o
  • New row format: fully off-page storage of long BLOB, TEXT, and VARCHAR columns
  • File format management: protects upward and downward compatibility
  • INFORMATION_SCHEMA tables: information about compression and locking
  • Link | Leave a comment |

    Comments {5}

    InnoDB Plugin "early adopter" release

    from: anonymous
    date: Dec. 4th, 2008 12:49 am (UTC)

    The announcement you link to contains this:

    "The InnoDB Team is glad to announce the availability of the early adopter release of the InnoDB Plugin 1.0.2."

    So, it sounds like the plugin itself is not GA. Rather, the announcement conveys that this release of the plugin is meant to function with the new GA release of MySQL 5.1.

    Reply | Thread

    Brian "Krow" Aker

    Re: InnoDB Plugin "early adopter" release

    from: krow
    date: Dec. 4th, 2008 12:56 am (UTC)

    Thanks! I've updated the post.

    Reply | Parent | Thread

    Mark Atwood

    (no subject)

    from: fallenpegasus
    date: Dec. 4th, 2008 05:04 am (UTC)

    Efficient handling of temp tables?

    Reply | Thread

    What about PBXT?

    from: ext_136524
    date: Dec. 4th, 2008 04:35 pm (UTC)

    I thought PBXT was one of the engines being looked at for being the "default" engine in Drizzle?

    Reply | Thread

    Brian "Krow" Aker

    Re: What about PBXT?

    from: krow
    date: Dec. 4th, 2008 05:10 pm (UTC)

    It is. Right now we have to ship with something as default, and Innodb is it. We are actively looking at PBXT.

    The hurdles with it are:

    1) It needs to pass all tests (I pushed some fixes for it myself last week).
    2) It needs to work on Solaris.

    Reply | Parent | Thread