Search Postgresql Archives

Re: Invocation overhead for procedural languages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 06/ago/08, at 16:04, Pavel Stehule wrote:

2008/8/6 Giorgio Valoti <giorgio_v@xxxxxxx>:
Hi all, I think I've read somewhere in the documentation that the invocation of functions written in procedural languages (with the exception of plpgsql) incur in performance hit due to the call the language interpreter. Is that
correct or am I completely off track?

it's depend. Start of interpret is only one overhead.
Other is date
conversions to language compatible types (without C and plpgsql).
Only plpgsql share expression evaluation with database, so it's
specific overhead only for plpgsql.

So is plpgsql slower on date conversion than other languages? Just curious: why does shared evaluation add some overhead?



[…]

but you can load perl after server start - look on preload_libraries
section in postgresql.conf

Nice to know.

Thank you Pavel
--
Giorgio Valoti

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux