Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 15:10:13
Message-ID: 49218955.6070209@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> 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.)
>
>
>

w.r.t. UTF8, I guess we'll need a way of knowing if we're preloading or
not, and if so we'd need to skip the calls to GetDatabaseEncoding().

I assume this will all happen in the 8.5 dev cycle (or later).

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-11-17 15:29:19 Re: Synchronous replication patch v2
Previous Message Andrew Chernow 2008-11-17 15:03:36 cygwin configure fails with thread-safety