Re: partition insert performance - Mailing list pgsql-admin

From Gurjeet Singh
Subject Re: partition insert performance
Date
Msg-id 65937bea0906151035v332ebba6rbe966f6d0e03be1e@mail.gmail.com
Whole thread Raw
In response to Re: partition insert performance  (Scott Marlowe <scott.marlowe@gmail.com>)
Responses Re: partition insert performance  (Scott Marlowe <scott.marlowe@gmail.com>)
List pgsql-admin
On Mon, Jun 15, 2009 at 10:57 PM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
On Mon, Jun 15, 2009 at 8:17 AM, Anj Adu<fotographs@gmail.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.

--
Lets call it Postgres

EnterpriseDB      http://www.enterprisedb.com

gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com
Mail sent from my BlackLaptop device

pgsql-admin by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: partition insert performance
Next
From: Scott Marlowe
Date:
Subject: Re: partition insert performance