Re: composite partition key or subpartitioning

From: Jaromir D.B. Nemec <>
Date: Tue, 29 Nov 2011 19:38:06 +0100
Message-ID: <B5C7D0487BD247F9B7EDE7EDFC8DDEC0_at_ADLA>

> partition by (time_id, application_id)
the main drawback of this schema is that is doesn't prune predicates like

tab1.time_id between 123 and 133 and tab1.application_id in (1,2)

this works fine with composite range - list partitioning

> . partitioned by time_id which is number representing day number from some
> time

If there are queries using DATE values (not direct the surrogate key) you may wont to check the post

HTH Jaromir D.B. Nemec

Received on Tue Nov 29 2011 - 12:38:06 CST

Original text of this message