RE: Why overhead of SPI is so large?

Поиск
Список
Период
Сортировка
От Tsunakawa, Takayuki
Тема RE: Why overhead of SPI is so large?
Дата
Msg-id 0A3221C70F24FB45833433255569204D1FCF47FD@G01JPEXMBYT05
обсуждение исходный текст
Ответ на Why overhead of SPI is so large?  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Ответы Re: Why overhead of SPI is so large?  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Список pgsql-hackers
From: Konstantin Knizhnik [mailto:k.knizhnik@postgrespro.ru]
> PL/pgSQL:   29044.361 ms
> C/SPI:          22785.597 ms
> 
> The fact that difference between PL/pgSQL and function implemented in C
> using SPI is not so large  was expected by me.

This PL/pgSQL overhead is not so significant compared with the three times, but makes me desire some feature like
Oracle'sALTER PROCEDURE ... COMPILE; that compiles the PL/SQL logic to native code.  I've seen a few dozen percent
speedup.
 


Regards
Takayuki Tsunakawa


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

Предыдущее
От: Thomas Munro
Дата:
Сообщение: Does TupleQueueReaderNext() really need to copy its result?
Следующее
От: Kyotaro Horiguchi
Дата:
Сообщение: Re: Remove page-read callback from XLogReaderState.