MySQL Forums
Forum List  »  Partitioning

Re: User requirements for MySQL Partitioning
Posted by: Mikael Ronström
Date: May 27, 2005 12:57PM

jey Razack wrote:
> > - Option to load any partition to cache
> (heap
> > storage engine may not help)
> >>Not sure which cache you refer to here?
> Load/ keep a copy of any parition in main memory.

This is most natural to solve on the handler level in MySQL. I'll keep it in mind
and see what I can do about it. It is probably possible to do something in the
partition handler as well but it is really tricky considering that it has to be integrated
with transaction logic. I'll also influence handler development to consider this

> Alter table <table_name> change partition
> <partition_name> cache = Y ( cache =N)
> > - Optimization hints for Index usage and
> other
> > select / join operations.
> >>Is there anything more than the normal
> FORCE INDEX you refer to here?
> 'Select' can span on many partitions, a hint can
> control how many max/min OS process/thread will be
> used for the select.

Ok. This is something I considered to do some parallelism on scanning
and then I agree that some hint for that is needed.

> I will list few more hints later...


> > - Don't allow to drop all the partitions.
> Atleast
> > the table must have one active partition.
> >>Sounds like something which should be
> configurable since I presume there
> are differing requirements here.
> Most of the DBAs automate the partitions' rotation
> and will accidently delete all the partitions. It
> will break all the applications and stored
> procedures. If DBA wants to delete all the
> partitions then he/she will use the 'DROP TABLE..'

I buy that argument.

Rgrds Mikael

Mikael Ronstrom
Senior Software Architect, MySQL AB
My blog:

Options: ReplyQuote

Written By
Re: User requirements for MySQL Partitioning
May 27, 2005 12:57PM

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.