| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Oleg Serov <serovov(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection; |
| Date: | 2008-11-17 05:10:06 |
| Message-ID: | 17760.1226898606@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim GÜNDÜZ | 2008-11-17 05:28:19 | Re: [HACKERS] pgsql: Enable script to generate preproc.y in build process. |
| Previous Message | Andrew Dunstan | 2008-11-17 04:59:15 | Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection; |