Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection; - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;
Date
Msg-id 17760.1226898606@sss.pgh.pa.us
Whole thread Raw
In response to Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;  (Andrew Dunstan <andrew@dunslane.net>)
Responses 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;  ("Robert Haas" <robertmhaas@gmail.com>)
List 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 by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;
Next
From: Devrim GÜNDÜZ
Date:
Subject: Re: [COMMITTERS] pgsql: Enable script to generate preproc.y in build process.