Postgres Pro
Downloads
Home   >   mailing lists

RE: Why overhead of SPI is so large? - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject RE: Why overhead of SPI is so large?
Date
Msg-id 0A3221C70F24FB45833433255569204D1FCF47FD@G01JPEXMBYT05
Whole thread Raw
In response to Why overhead of SPI is so large?  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Responses Re: Why overhead of SPI is so large?  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
List pgsql-hackers
Tree view 
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 by date:

Previous
From: Thomas Munro
Date:
Subject: Does TupleQueueReaderNext() really need to copy its result?
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Remove page-read callback from XLogReaderState.