[MDEV-4618] why we use WITH_PARTITION_STORAGE_ENGINE ? Created: 2013-06-05  Updated: 2013-06-05  Resolved: 2013-06-05

Status: Closed
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: Task Priority: Trivial
Reporter: roberto spadim Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None


 Description   

hi guys, it's a idiot question, but why we use WITH_PARTITION_STORAGE_ENGINE?

could partition be default in any version? partition_storage is a big footprint for embedded that a configure option must exists?

 Comments   
Comment by Sergei Golubchik [ 2013-06-05 ]

it could.
configure option exists for all storage engines that technically can be disabled. partition engine is one of those.

Comment by roberto spadim [ 2013-06-05 ]

but for example, partition should change query cache invalidation (table + partition_id), and meta data lock (lock of partition 1234 of table xxx, instead of only table xxxx)
is not simplier consider that all table have partitions?

Comment by roberto spadim [ 2013-06-05 ]

other doubt, why partition isnt listed as engine in information schema?

Generated at Thu Feb 08 06:57:47 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.