| From: | pginfo <pginfo(at)t1(dot)unisoftbg(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: left join performance problem |
| Date: | 2003-06-12 04:48:27 |
| Message-ID: | 3EE8061B.1FAED8AD@t1.unisoftbg.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Many thanks Tom,
the doc do not contain solution for this case, but the idea to
change the join order was excelent and all is working fine at the moment.
regards,
ivan.
Tom Lane wrote:
> pginfo <pginfo(at)t1(dot)unisoftbg(dot)com> writes:
> > I have a big problem with pg left join performance.
>
> I think the problem is that the LEFT JOIN clause is forcing the
> planner to join A_SKLAD to A_MESKLAD before anything else, whereas
> a good plan would do some of the other joins first to eliminate
> as many rows as possible. You will need to revise the query to
> let the LEFT JOIN happen later. For discussion see
> http://www.postgresql.org/docs/view.php?version=7.3&idoc=0&file=explicit-joins.html
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kostyrka | 2003-06-12 09:32:09 | Re: Table Relationships |
| Previous Message | Tom Lane | 2003-06-12 02:57:51 | Re: left join performance problem |