Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Support for sub-partitioning #26

Closed
keithf4 opened this Issue · 3 comments

2 participants

@keithf4
Owner

Implement a method to allow child tables to themselves be parent tables of another partition set.

@keithf4 keithf4 added the enhancement label
@keithf4 keithf4 self-assigned this
@keithf4
Owner

Added in 1.8.0

@keithf4 keithf4 closed this
@davidblewett

Does this mean that data remains in the intermediate levels of the chain? I.e., in your example "Sub-partition Time->Time->Time: Yearly -> Monthly -> Daily", does data remain in the Yearly and Monthly partitions? Or does it only finally reside in the Daily set?

@keithf4
Owner

It resides in the lowest level (daily in this case). The main advantage of subpartitioning in postgresql is to avoid the constraint exclusion checks and directly query the exact interval of data that you're looking for by explicitly naming the partition instead of using a WHERE clause. It's only really a concern with extremely large data sets that I've seen. But I had many people asking me for this feature at conferences (one person I know that actually had such large data sets), so I put the work into doing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.