10bet网址
MySQL 8.0 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr)- 41.6Mb
PDF (A4)- 41.7Mb
Man Pages (TGZ)- 262.2Kb
Man Pages (Zip)- 372.3Kb
Info (Gzip)- 4.0Mb
Info (Zip)- 4.0Mb
Excerpts from this Manual

24.2.6 Subpartitioning

Subpartitioning—also known ascomposite partitioning—is the further division of each partition in a partitioned table. Consider the followingCREATE TABLEstatement:

创建表ts (INT id,购买日期)分区BY RANGE( YEAR(purchased) ) SUBPARTITION BY HASH( TO_DAYS(purchased) ) SUBPARTITIONS 2 ( PARTITION p0 VALUES LESS THAN (1990), PARTITION p1 VALUES LESS THAN (2000), PARTITION p2 VALUES LESS THAN MAXVALUE );

Tabletshas 3RANGEpartitions. Each of these partitions—p0,p1, andp2—is further divided into 2 subpartitions. In effect, the entire table is divided into3 * 2 = 6partitions. However, due to the action of thePARTITION BY RANGEclause, the first 2 of these store only those records with a value less than 1990 in thepurchasedcolumn.

It is possible to subpartition tables that are partitioned byRANGEorLIST. Subpartitions may use eitherHASHorKEYpartitioning. This is also known ascomposite partitioning.

Note

SUBPARTITION BY HASHandSUBPARTITION BY KEYgenerally follow the same syntax rules asPARTITION BY HASHandPARTITION BY KEY, respectively. An exception to this is thatSUBPARTITION BY KEY(unlikePARTITION BY KEY) does not currently support a default column, so the column used for this purpose must be specified, even if the table has an explicit primary key. This is a known issue which we are working to address; seeIssues with subpartitions, for more information and an example.

It is also possible to define subpartitions explicitly usingSUBPARTITIONclauses to specify options for individual subpartitions. For example, a more verbose fashion of creating the same tabletsas shown in the previous example would be:

创建表ts (INT id,购买日期)分区BY RANGE( YEAR(purchased) ) SUBPARTITION BY HASH( TO_DAYS(purchased) ) ( PARTITION p0 VALUES LESS THAN (1990) ( SUBPARTITION s0, SUBPARTITION s1 ), PARTITION p1 VALUES LESS THAN (2000) ( SUBPARTITION s2, SUBPARTITION s3 ), PARTITION p2 VALUES LESS THAN MAXVALUE ( SUBPARTITION s4, SUBPARTITION s5 ) );

Some syntactical items of note are listed here:

  • 每一个partition must have the same number of subpartitions.

  • If you explicitly define any subpartitions usingSUBPARTITIONon any partition of a partitioned table, you must define them all. In other words, the following statement fails:

    创建表ts (INT id,购买日期)分区BY RANGE( YEAR(purchased) ) SUBPARTITION BY HASH( TO_DAYS(purchased) ) ( PARTITION p0 VALUES LESS THAN (1990) ( SUBPARTITION s0, SUBPARTITION s1 ), PARTITION p1 VALUES LESS THAN (2000), PARTITION p2 VALUES LESS THAN MAXVALUE ( SUBPARTITION s2, SUBPARTITION s3 ) );

    This statement would still fail even if it usedSUBPARTITIONS 2.

  • 每一个SUBPARTITIONclause must include (at a minimum) a name for the subpartition. Otherwise, you may set any desired option for the subpartition or allow it to assume its default setting for that option.

  • Subpartition names must be unique across the entire table. For example, the followingCREATE TABLEstatement is valid:

    创建表ts (INT id,购买日期)分区BY RANGE( YEAR(purchased) ) SUBPARTITION BY HASH( TO_DAYS(purchased) ) ( PARTITION p0 VALUES LESS THAN (1990) ( SUBPARTITION s0, SUBPARTITION s1 ), PARTITION p1 VALUES LESS THAN (2000) ( SUBPARTITION s2, SUBPARTITION s3 ), PARTITION p2 VALUES LESS THAN MAXVALUE ( SUBPARTITION s4, SUBPARTITION s5 ) );