MySQL Forums
Forum List  »  Partitioning

Partitioning by range and ALTER with DROP and SELECT
Posted by: Chiara Chiara
Date: May 12, 2008 09:51AM


My question is related to 5.1.24-rc and partitioning by range (using InnodB as storage engine) and waiting selects while during ALTER with DROP partition.

the paragraph related to Table locks says:

Table locks.
The process executing a partitioning operation on a
table takes a write lock on the table. Reads from such
tables are relatively unaffected; pending INSERT and
UPDATE operations are performed as soon as the
partitioning operation has completed

Is that true also for the InnoDB storage engine ?
What does "Reads from such tables are relatively
unaffected;" implies, please ?

I have noticed that while doing a set of SELECT
statements on one of the partitions (e.g. p1) and
the same time doing an ALTER TABLE with drop or add
a different partition (e.g. ALTER TABLE DROP or ADD
PARTITION p10) all the select
statements are placed on hold (Waiting for table).

Is there any workaround to avoid the set of selects to be placed on hold ?

Thanks your help,


Options: ReplyQuote

Written By
Partitioning by range and ALTER with DROP and SELECT
May 12, 2008 09:51AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.