Re: Open tables with Partitioning
There is overhead when opening a partitioned table, since every partitions handler needs to be opened (which also will require additional handler memory etc.)
For InnoDB it currently have multiple copies of the InnoDB metadata/datadict, since that is stored within the handler, but the table level metadata will not be duplicated.
So opening a partitioned table will take more time if there is a lot of partitions, compared to a non partitioned table. Note however that the opened table is cached in the table cache and will be reused without the need of closing and opening it again.
The current problem is locking which is done for every statement. See bug#37252. I am currently working on fixing this by implementing WL#4443.
Subject
Views
Written By
Posted
4608
February 28, 2011 04:56AM
1733
February 28, 2011 10:03AM
2242
March 01, 2011 11:22PM
2465
March 02, 2011 03:06AM
1608
March 02, 2011 07:16AM
Re: Open tables with Partitioning
1767
March 02, 2011 07:29AM
1652
March 02, 2011 07:46AM
2440
March 02, 2011 08:20AM
1618
March 02, 2011 11:29AM
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.