| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | hs(at)cybertec(dot)at |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PREPARE / EXECUTE |
| Date: | 2002-10-23 16:20:42 |
| Message-ID: | 20021023162042.GA7032@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 23, 2002 at 18:04:01 +0200,
Hans-Jürgen Schönig <postgres(at)cybertec(dot)at> 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.
One option you have is to explicitly give the join order. You can look at
explain to see what order the joins are done in and then rewrite the sql
to force them to be done in that order. This should keep things simple
for the planner.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luis Alberto Amigo Navarro | 2002-10-23 16:33:53 | Re: crashes with postgresql 7.2.1 on IRIX 6.5 |
| Previous Message | Tom Lane | 2002-10-23 16:15:11 | Re: PREPARE / EXECUTE |