I found that there is a new feature called updatable merge table in the new release (Updatable merge tables with partition predicates). I think this makes merge table similar to partitioned table in other databases. But I found that the upper bound of range partitioning is an inclusive bound, while the upper bound of some databases like MySQL and PostgreSQL is an exclusive bound.

    So my question is: why is the upper bound declaration designed like this? Will it be possible if MonetDB be consistent with other databases?

    Besides, currently merge table doesn't support partition pruning, so all child tables will be scanned even if the filter condition contains the partitioning key. Is it possible if this feature will be added one day?

Best Regards,

Yinjie Lin