Re: partition insert performance

On Mon, Jun 15, 2009 at 11:35 AM, Gurjeet Singh<singh(dot)gurjeet(at)gmail(dot)com> wrote:
> On Mon, Jun 15, 2009 at 10:57 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
> wrote:
>>
>> On Mon, Jun 15, 2009 at 8:17 AM, Anj Adu<fotographs(at)gmail(dot)com> wrote:
>> > We currently use triggers with static if..then..else statements to
>> > determine
>> > which partition the data goes into. Would there be a performance impact
>> > if
>> > we were to use dynamic sql to achieve the same ?. The issue with static
>> > triggers is the maintenance overhead of having to redefine the triggers
>> > periodically. The dynamic sql is simple and involves building a sql
>> > string
>> > with just a to_char(date_Field) to determine which partition the data
>> > goes
>> > into and the trigger will never have to be re-defined.
>>
>> If you're using plpgsql prepare for a world of pain if you've got any
>> null values in your inserts.
>
> :) Using COALESCE isn't that bad.

In my experience it's WAY more than just coalesce.