Re: partition insert performance
| От | Tom Lane |
|---|---|
| Тема | Re: partition insert performance |
| Дата | |
| Msg-id | 21164.1245090954@sss.pgh.pa.us обсуждение |
| Ответ на | Re: partition insert performance (Scott Marlowe <scott.marlowe@gmail.com>) |
| Ответы |
Re: partition insert performance
|
| Список | pgsql-admin |
Scott Marlowe <scott.marlowe@gmail.com> writes:
> On Mon, Jun 15, 2009 at 11:35 AM, Gurjeet Singh<singh.gurjeet@gmail.com> wrote:
>> On Mon, Jun 15, 2009 at 10:57 PM, Scott Marlowe <scott.marlowe@gmail.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
В списке pgsql-admin по дате отправления: