Re: partition insert performance
| От | Anj Adu |
|---|---|
| Тема | Re: partition insert performance |
| Дата | |
| Msg-id | f2fd819a0906151326u205975rbc8ea7d1298ca548@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: partition insert performance (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-admin |
Thanks to all for your advice. I will stay away from dynamic sql. The current implementation of static date comparisons in the trigger is lightning fast..(we have over 50 million inserts per day). I will bite the maintenance overhead as I cannot compromise on performance.
On Mon, Jun 15, 2009 at 11:35 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
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 anyquote_nullable() would really be the right thing for inserts. However,
>>> null values in your inserts.
>>
>> :) Using COALESCE isn't that bad.
> In my experience it's WAY more than just coalesce.
I think the short answer to the OP's question is that dynamic SQL will
lose big-time performancewise.
regards, tom lane
В списке pgsql-admin по дате отправления: