Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;
От | Tom Lane |
---|---|
Тема | Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection; |
Дата | |
Msg-id | 17760.1226898606@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection; (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: Pl/Perl function: Speed of the First time executing
pl/perl function in connection;
Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection; |
Список | pgsql-hackers |
Andrew Dunstan <andrew@dunslane.net> writes: > Tom Lane wrote: >> So about the only real answer is going to be preloading. It seems worth >> considering that on machines where can_run_two is true, we should just >> go ahead and initialize both interps at _PG_init time, so as to allow >> the "require Safe" overhead to be bought back by preloading. > Even if only one language is defined? The point here is to do the work at postmaster start time. You won't get a chance to find out whether both languages are defined in some database or other. (This is the same thing as the point about the UTF8 hack --- you can't tell if it's needed or not.) regards, tom lane
В списке pgsql-hackers по дате отправления: