On Mon, Jun 15, 2009 at 10:57 PM, Scott Marlowe <scott.marlowe@xxxxxxxxx> wrote:
If you're using plpgsql prepare for a world of pain if you've got anyOn Mon, Jun 15, 2009 at 8:17 AM, Anj Adu<fotographs@xxxxxxxxx> 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.
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
