Re: PL/pgSQL and shared_preload_libraries

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PL/pgSQL and shared_preload_libraries
Date: 2010-11-06 16:04:14
Message-ID: 20129.1289059454@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Since we now install PL/pgSQL by default, should we configure
> shared_preload_libraries to preload PL/pgSQL?

I don't think that follows. The fact that it's there doesn't mean
everyone is using it. In any case, I've seen no evidence that says
you'd get a performance win this way. The preload feature is meant
for modules that do a substantial amount of work at load time, which
plpgsql does not.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2010-11-06 16:16:41 Should we use make -k on the buildfarm?
Previous Message Tom Lane 2010-11-06 15:53:00 Re: SQL functions that can be inlined