Re: partition insert performance

Hi,

Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
> 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:
>>> 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.

There's this trick:

v_sql := 'INSERT INTO schema.parent_' || to_char(NEW.date, 'YYYYMM') ||
' SELECT (' || quote_literal(textin(record_out(NEW))) || '::schema.parent).*;';

EXECUTE v_sql;

This will handle dynamic SQL and NULLs correctly, but as said already
won't match static SQL in term of performances. Just saying for people
searching simplifications.

Regards,
--
dim