From: Johnny Kristensen <johnnybo1@mail.tele.dk>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: SQL Functions vs PL/PgSQL
Date: Fri, 14 Feb 2003 10:12:39 +0100
Message-ID: <005a01c2d409$39f6b960$dc9ac450@johnny> (raw)
References: <000801c2d2e0$edd32420$dc9ac450@johnny>
<200302130902.05987.josh@agliodbs.com>
Of course what I meant was if postgres stores execution plans for queries in user-defined SQL functions. From the docs I can see that PL/PgSQL uses the SPI-interface to create and store execution plans for queries for each connection. But I'll use the PREPARE function like Thomasz Myrta suggested.
/Johnny
----- Original Message -----
From: "Josh Berkus" <josh@agliodbs.com>
To: "Johnny Kristensen" <johnnybo1@mail.tele.dk>; <pgsql-sql@postgresql.org>
Sent: Thursday, February 13, 2003 6:02 PM
Subject: Re: [SQL] SQL Functions vs PL/PgSQL
Johnny,
> Does postgres store execution plan's for user-defined SQL functions as the
> PL/pgSQL interpreter does. And if so - will this only be prepared after an
> initial call to the function? Can't seem to find this information in the
> docs!? Thanks,
Unless you know something I don't, I do not believe that PL/pgSQL stores
execution plans for functions.
--
Josh Berkus
Aglio Database Solutions
San Francisco
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: johnnybo1@mail.tele.dk, josh@agliodbs.com
Subject: Re: SQL Functions vs PL/PgSQL
In-Reply-To: <005a01c2d409$39f6b960$dc9ac450@johnny>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox