Re: Benchmarking partitioning triggers and rules

Поиск
Список
Период
Сортировка
От Tim Uckun
Тема Re: Benchmarking partitioning triggers and rules
Дата
Msg-id CAGuHJrPZjjZSuc_TbH+rymax2AdDq3XgSjX8FW_-0ZGhTpszrg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Benchmarking partitioning triggers and rules  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Ответы Re: Benchmarking partitioning triggers and rules  (Adrian Klaver <adrian.klaver@aklaver.com>)
Список pgsql-general
I understand that there is overhead involved in parsing the strings and such.  The amount of overhead was surprising to me but that's another matter.  What I am really puzzled about is the difference between the statements

EXECUTE  'INSERT INTO ' ||  quote_ident(partition_name) ||  ' SELECT ($1).*' USING NEW ;

and

  EXECUTE  'INSERT INTO ' ||  quote_ident(partition_name) ||  ' VALUES (($1).*)' USING NEW ;

They both do string interpolation but one is significantly faster than the other.   Is there a third and even faster way?

I am using RDS so I can't really do stored procs in C.

В списке pgsql-general по дате отправления:

Предыдущее
От: Jim Nasby
Дата:
Сообщение: Re: Working with Array of Composite Type
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: Benchmarking partitioning triggers and rules