| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Anj Adu <fotographs(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: partition insert performance |
| Date: | 2009-06-15 17:27:30 |
| Message-ID: | dcc563d10906151027v53a35449m1ea3b58c0e172828@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2009-06-15 17:35:33 | Re: partition insert performance |
| Previous Message | Iñigo Martinez Lasala | 2009-06-15 15:51:33 | Re: Log full with gigabyes of CurTransactionContex |