To: =?KOI8-U?B?96bUwcymyiD0yc3eydvJzg==?= <tivv00@gmail.com>
cc: pgsql-performance@postgresql.org
Subject: Re: Planner not using column limit specified for one column for
	another column equal to first
In-reply-to: <m2y331e40661004160102tff445f9eg165a04efe3b409ed@mail.gmail.com> 
References: <m2y331e40661004160102tff445f9eg165a04efe3b409ed@mail.gmail.com>
Comments: In-reply-to =?KOI8-U?B?96bUwcymyiD0yc3eydvJzg==?= <tivv00@gmail.com>
	message dated "Fri, 16 Apr 2010 11:02:06 +0300"
Date: Fri, 16 Apr 2010 10:19:47 -0400
Message-ID: <8534.1271427587@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

=?KOI8-U?B?96bUwcymyiD0yc3eydvJzg==?= <tivv00@gmail.com> writes:
> I've thought and someone in this list've told me that this should be done
> automatically.

No, that's not true.  We do make deductions about transitive equalities,
ie, given WHERE a=b AND b=c the planner will infer a=c and use that if
it's helpful.  We don't make deductions about inequalities such as a>c.
In theory there's enough information available to do so, but overall
trying to do that would probably waste more cycles than it would save.
You'd need a lot of expensive new planner infrastructure, and in the
vast majority of queries it wouldn't produce anything very helpful.

As was pointed out, even if we had such logic it wouldn't apply in this
example, because the equality conditions aren't real equalities but
OUTER JOIN conditions.

			regards, tom lane