From: Richard Huxton <dev@archonet.com>
To: Joe Conway <mail@joeconway.com>
Subject: Re: Which is faster SQL or PL/PGSQL
Date: Mon, 20 Oct 2003 18:49:19 +0100
User-Agent: KMail/1.5
Cc: Michael Pohl <pgsql@newtopia.com>, pgsql-sql@postgresql.org,
	"George A.J" <jinujosein@yahoo.com>
References: <Pine.LNX.4.44.0310201119240.10378-100000@server1.techplant.com>
	<200310201809.51830.dev@archonet.com>
	<3F941A43.1040802@joeconway.com>
In-Reply-To: <3F941A43.1040802@joeconway.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310201849.19668.dev@archonet.com>

On Monday 20 October 2003 18:24, Joe Conway wrote:
> Richard Huxton wrote:
> > So - gain by not re-planning on every call, but maybe lose because your
> > plan is not so precise.
> >
> > Of course, any queries you build dynamically and run via EXECUTE will
> > have to be planned each time.
>
> This question gets even more complex in 7.4, where many simple SQL
> functions will get inlined, and library preloading is available to speed
> that first PL/pgSQL call.

What will be the effects of inlining? Does it mean the planner merges the 
function's plan into the larger query?

-- 
  Richard Huxton
  Archonet Ltd