On Thu, May 28, 2009 at 6:43 PM, Anj Adu <
fotographs@gmail.com> wrote:
> Partitioning is implemented via rules and check constraints to ensure
> partition integrity.
>
> On Thu, May 28, 2009 at 5:21 PM, Scott Marlowe <
scott.marlowe@gmail.com>
> wrote:
>>
>> On Thu, May 28, 2009 at 5:22 PM, Anj Adu <
fotographs@gmail.com> wrote:
>> > I noticed a very strange performance issue after I pre-create daily
>> > partitions for the next month on a table that has a very large insert
>> > volume
>> > (30 million a day). After the partitions are created..the inserts seem
>> > to
>> > slow down. I verifiied that this was the issue by dropping the
>> > partitions...When I dropped the pre-created partitions..the performance
>> > issue disappeared. Looks like you cannot have too many partitions (in
>> > this
>> > case..I had a total of 35 partitions when the performance issue was
>> > noticed)
>>
>> How are you enforcing partiitoning on your inserts? Via app
>> knowledge, triggers, or rules? I'd expect rules might have a penalty
>> with more partitions, but not expect it from app or trigger based
>> partitioning.
>
>