From: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
---|---|
To: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Removing Inner Joins |
Date: | 2013-07-10 02:59:11 |
Message-ID: | CAFjFpRcZw0=oDhcrCNNWZUwKY=DajLVL0VhgC4oB-isXK6-NBA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
AFAIK,
There is code to remove the redundant relations (joins too are relations).
But I don't remember exactly where it is. Start looking at query_planner().
The removal of relations should happen before actually planning the joins.
On Tue, Jul 9, 2013 at 12:21 PM, Atri Sharma <atri(dot)jiit(at)gmail(dot)com> wrote:
> My main point here is researching how difficult it is to add
> functionality in the planner to allow it to to detect and make
> decisions on foreign keys present in the outer relation.
>
> I think that if this is added, rest of the work would be much easier.
> I amy be completely wrong,though.
>
> Thoughts/Comments?
>
> Regards,
>
> Atri
>
> Regards,
>
> Atri
> l'apprenant
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
--
Best Wishes,
Ashutosh Bapat
EntepriseDB Corporation
The Postgres Database Company
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2013-07-10 03:24:28 | Re: Performance Improvement by reducing WAL for Update Operation |
Previous Message | Tatsuo Ishii | 2013-07-10 01:19:41 | pgbench patches |