Re:Designing DB partitions you don't have to babysit
by toledocavani on Saturday July 04, 2026 @11:36PM
(#48791047)
And the post did mention it, argueing it may be better to partition by auto-incremented ID with the support of catch-all range and partution monitoring.
> The primary key already exists. For tables using BIGINT AUTO_INCREMENT, it’s monotonically increasing: newer rows have larger IDs. That’s the property range partitioning needs. The primary key is the partition key.
> The primary key already exists. For tables using BIGINT AUTO_INCREMENT, it’s monotonically increasing: newer rows have larger IDs. That’s the property range partitioning needs. The primary key is the partition key.