• user warning: Table './avideotutorial/votingapi_vote' is marked as crashed and last (automatic?) repair failed query: SELECT * FROM votingapi_vote v WHERE 1 = 1 AND v.content_type = 'node' AND v.content_id = 196 AND v.tag = 'upndown' AND v.uid = 0 AND v.vote_source = '47.128.63.2' AND v.timestamp >= 1734784125 in /data/avideotutorial/sites/all/modules/votingapi/votingapi.module on line 557.
  • user warning: Table './avideotutorial/votingapi_vote' is marked as crashed and last (automatic?) repair failed query: SELECT * FROM votingapi_vote v WHERE 1 = 1 AND v.content_type = 'node' AND v.content_id = 196 AND v.tag = 'upndown' AND v.uid = 0 AND v.vote_source = '47.128.63.2' AND v.timestamp >= 1734784125 in /data/avideotutorial/sites/all/modules/votingapi/votingapi.module on line 557.

Partitioning in MySQL 5.1


Sheeri Cabral of the Pythian Group (http://www.pythian.com) presented a session on the new partitioning feature in MySQL 5.1 at the January 2009 Boston User Group.

From her description:
I go through how to define partitions, how partitioning makes queries faster, the different types of partitioning and when to use each type, and the restrictions and limitations of partitioning.

The slides are available at http://www.technocation.org/files/doc/2009_01_Partitioning.pdf

Notes:
The partitioning part of the MySQL Manual is at: http://dev.mysql.com/doc/refman/5.1/en/partitioning-overview.html.

The functions that are not allowed in partitioning expressions are listed at: http://dev.mysql.com/doc/refman/5.1/en/partitioning-limitations.html

We also had an interesting development — according to the manual, an INSERT to a partitioned table that includes values that do not have a partition should insert all values up to the failure point. The example I used (and that you can see in the video) is:

insert into nums_list_mod (id) VALUES (4001, 4004, 4002);

Where 4001 and 4002 fit into partitions but there is no partition defined that will accept 4004. According to the manual, the value 4001 should be inserted, but 4004 and 4002 should not. Instead, we got the behavior that nothing was inserted (sql_mode= and this was not within a transaction).

Enjoy the presentation!


See video

Comments

Unfortunately the key buffer

Unfortunately the key buffer iteslf has a big fat mutex around it (one per key buffer, that is, just one unless you use multiple key buffers), which is taken any time anyone modifies the key buffer (which includes bringing pages in AND out of it, which is done by selects as well as updates).This means that operations which do a large amount of key buffer work effectively block up the entire server even if they're operating on an entirely different table.The example we see, is doing a lot of inserts with DELAY_KEY_WRITE on, then doing a flush table on that table. It effectively stops the world during the flush no index on any table at all may be touched whatsoever.

Post new comment

  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options