Hi,
Scott Marlowe writes:
> On Mon, Jun 15, 2009 at 11:35 AM, Gurjeet Singh
> wrote:
>> On Mon, Jun 15, 2009 at 10:57 PM, Scott Marlowe
>> wrote:
>>> 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.
>
Thanks to all for your advice. I will stay away from dynamic sql. The
current implementation of static date comparisons in the trigger is
lightning fast..(we have over 50 million inserts per day). I will bite the
maintenance overhead as I cannot compromise on performance.
On Mon, Jun 15, 2009 at 1
Scott Marlowe writes:
> On Mon, Jun 15, 2009 at 11:35 AM, Gurjeet Singh
> wrote:
>> On Mon, Jun 15, 2009 at 10:57 PM, Scott Marlowe
>> wrote:
>>> 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
On Mon, Jun 15, 2009 at 11:35 AM, Gurjeet Singh wrote:
> On Mon, Jun 15, 2009 at 10:57 PM, Scott Marlowe
> wrote:
>>
>> On Mon, Jun 15, 2009 at 8:17 AM, Anj Adu wrote:
>> > We currently use triggers with static if..then..else statements to
>> > determine
>> > which partition the data goes into. Wo
On Mon, Jun 15, 2009 at 10:57 PM, Scott Marlowe wrote:
> On Mon, Jun 15, 2009 at 8:17 AM, Anj Adu 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 sq
On Mon, Jun 15, 2009 at 8:17 AM, Anj Adu 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 mai
On Mon, Jun 15, 2009 at 7:47 PM, Anj Adu 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 m
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
per
