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
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 <postgres(at)cybertec(dot)at> wrote:
>>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
www.postgresql.at <http://www.postgresql.at>, cluster.postgresql.at
<http://www.cybertec.at>, kernel.cybertec.at <http://kernel.cybertec.at>
In response to
pgsql-hackers by date
|Next:||From: Greg Copeland||Date: 2002-10-23 17:52:34|
|Subject: Re: PREPARE / EXECUTE|
|Previous:||From: Nicolae Mihalache||Date: 2002-10-23 16:46:41|
|Subject: Re: crashes with postgresql 7.2.1 on IRIX 6.5|