First of all PREPARE/EXECUTE is a wonderful thing to speed up things
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
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.
*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://www.cybertec.at>, kernel.cybertec.at <http://kernel.cybertec.at>
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2002-10-23 14:24:58|
|Subject: Re: pg_dump and large files - is this a problem?|
|Previous:||From: Manfred Koizar||Date: 2002-10-23 14:19:45|
|Subject: Re: BTree free pages again|