| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, Anj Adu <fotographs(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: partition insert performance |
| Date: | 2009-06-15 18:35:54 |
| Message-ID: | 21164.1245090954@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
quote_nullable() would really be the right thing for inserts. However,
I think the short answer to the OP's question is that dynamic SQL will
lose big-time performancewise.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Polishchuk | 2009-06-15 20:15:30 | Is IDLE session really idle? |
| Previous Message | Scott Marlowe | 2009-06-15 18:32:09 | Re: partition insert performance |