MySQL Forums
Forum List  »  Partitioning

Re: Partitioning in MySQL: Range Partitioning
Posted by: Mikael Ronström
Date: July 01, 2005 03:24PM

Hi,

Mohamed OUADOU wrote:
> Hi,
>
> As an idea for table partitionning, it will be
> very interessting when working with large table to
> allow both partitions and subpartitions .
> For example, a table partitionned by year can have
> a year partition divided in 12 subpartitions for
> each month of the year.
>

Sounds good, this is part of what will be supported from the start.

> Another idea is to allow for example round robin
> partitionning, in order to increase write
> performance! Read performance can also be
> increased since it can be done in parallel mode.
>

Round Robin partitioning I've heard mentioned before and I remember
that the logic behind it was plausible but I keep forgetting why not
Hash partitioning is better since then I can also in some cases prune away
a number of partitions not needing to be scanned.

> As drop partition, it will be very interesting
> to allow data partition moving to a table. In
> some applications monthly data archiving is
> needed, as an example after each month the
> partition aged more than 1 year will be moved to a
> table named ARCHIVE_T_(year-1)_month.
>

I'll take that into account when doing the work on ADD/DROP/MERGE partitions.
It looks like it could be done very easily actually.

> ALTER TABLE T move PARTITION P0 TO TABLE
> ARCHIVE_T_0_MONTH;
>

Thx for your input and if you have more clarification regarding Round Robin Partitioning
I'd be happy. It is not very difficult to add support for it, I am just not fully convinced yet
that there exists situations when it is superior to all other variants.

Rgrds Mikael

>
> Rgrds
> Mohamed OUADOU
> Database Architect

Mikael Ronstrom
Senior Software Architect, MySQL AB
My blog: http://mikaelronstrom.blogspot.com

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Partitioning in MySQL: Range Partitioning
3224
July 01, 2005 03:24PM


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.