If you were using them that frequently, couldn't you just keep a persistent connection? If it's not used that often, wouldn't the overhead of preparing the query following a new connection become noise?
Greg On Wed, 2002-10-23 at 09:24, Hans-Jürgen Schönig wrote: > First of all PREPARE/EXECUTE is a wonderful thing to speed up things > significantly. > I wonder if there is a way to store a parsed/rewritten/planned query in > a table so that it can be loaded again. > > This might be useful when it comes to VERY complex queries (> 10 tables). > I many applications the situation is like that: > > a. The user connects to the database. > b. The user sends various different queries to the server (some might be > the same) > c. The user disconnects. > > If there was a way to store execution plans in a table the user could > load the execution plans of the most time consuming stuff into the > backend without parsing and optimizing it every time he authenticates. > > Does it sound useful to anybody? Is it possible to do it or are there > some technical problems? > > Maybe this is worth thinking about. > > Hans > > -- > *Cybertec Geschwinde u Schoenig* > Ludo-Hartmannplatz 1/14, A-1160 Vienna, Austria > Tel: +43/1/913 68 09; +43/664/233 90 75 > www.postgresql.at <http://www.postgresql.at>, cluster.postgresql.at > <http://cluster.postgresql.at>, www.cybertec.at > <http://www.cybertec.at>, kernel.cybertec.at <http://kernel.cybertec.at> > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html