From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ehab Galal <ehabgalal123(at)hotmail(dot)com> |
Cc: | "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: omitting redundant join predicate |
Date: | 2007-11-05 16:08:13 |
Message-ID: | 20749.1194278893@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Ehab Galal <ehabgalal123(at)hotmail(dot)com> writes:
> what i expected is that the optimizer will use the redundant predicates
> to create the plan, but the execution plan itself will not execute a
> redundant predicate.
> O! I see, it's my mistake. The example i mentioned was not a good example. I tried the equality and it is working well :)
The planner has a great deal more smarts about equality conditions than
inequality conditions. There's more you can do with equalities, and
it's more useful for typical queries.
> I am using postgresql 8.5.1, I am wondering is there is any patch that
> i can run to enable it to put the actual table names instead of
> inner/outer.
Update to 8.2.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Joseph Krogh | 2007-11-05 16:33:10 | Re: Returning the total number of rows as a separate column when using limit |
Previous Message | Gregory Stark | 2007-11-05 15:27:03 | Re: Returning the total number of rows as a separate column when using limit |