This is exactly what we do in case of complex stuff. I know that it can help to reduce the problem for the planner.
However: If you have explicit joins across 10 tables the SQL statement is not that readable any more and it is still slower than a prepared execution plan.

I guess it is worth thinking about prepared plans somewhere on disk.
Is there a way to transform ASCII -> plan?


Bruno Wolff III wrote:

On Wed, Oct 23, 2002 at 18:04:01 +0200,
Hans-Jürgen Schönig <[EMAIL PROTECTED]> wrote:

An example:
I have a join across 10 tables + 2 subselects across 4 tables
on the machine I use for testing:
planner: 12 seconds
executor: 1 second

The application will stay the same forever.
I could be 10 times faster if there was a way to load the execution plan into the backend.

*Cybertec Geschwinde u Schoenig*
Ludo-Hartmannplatz 1/14, A-1160 Vienna, Austria
Tel: +43/1/913 68 09; +43/664/233 90 75 <>, <>, <>, <>

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

Reply via email to