| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
| Cc: | hs(at)cybertec(dot)at, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PREPARE / EXECUTE |
| Date: | 2002-10-23 16:15:11 |
| Message-ID: | 2038.1035389711@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruno Wolff III <bruno(at)wolff(dot)to> writes:
> Hans-Jrgen Schnig <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
> One option you have is to explicitly give the join order.
Yes, this is exactly the sort of situation where forcing the join order
is a big performance win. See
http://www.ca.postgresql.org/users-lounge/docs/7.2/postgres/explicit-joins.html
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2002-10-23 16:20:42 | Re: PREPARE / EXECUTE |
| Previous Message | Nicolae Mihalache | 2002-10-23 16:09:07 | Re: crashes with postgresql 7.2.1 on IRIX 6.5 |