PREPARE / EXECUTE

From: Hans-Jürgen Schönig <postgres(at)cybertec(dot)at>
To: pgsql-hackers(at)postgresql(dot)org
Subject: PREPARE / EXECUTE
Date: 2002-10-23 14:24:27
Message-ID: 3DB6B11B.4020107@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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>

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-10-23 14:24:58 Re: pg_dump and large files - is this a problem?
Previous Message Manfred Koizar 2002-10-23 14:19:45 Re: BTree free pages again