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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "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 17:57:26
Message-ID: 5210.1226944646@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Robert Haas" <robertmhaas(at)gmail(dot)com> writes:
>> The point here is to do the work at postmaster start time.

> What happens if I upgrade one of the perl modules that is getting
> preloaded here? It seems this change will require the entire database
> to be shut down to pick up the changes, vs. just needing to terminate
> individual backends.

Well, that would be one of the tradeoffs to consider when deciding
to preload plperl.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2008-11-17 18:04:45 Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;
Previous Message Robert Haas 2008-11-17 17:56:09 Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;