From: Manfred Koizar <mkoi-pg@aon.at>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephan Szabo <sszabo@megazone.bigpanda.com>,
	Dani Oderbolz <oderbolz@ecologic.de>, pgsql-hackers@postgreSQL.org
Subject: Re: [SQL] "SELECT IN" Still Broken in 7.4b 
Date: Thu, 21 Aug 2003 23:18:04 +0200
Message-ID: <p0dakv05anhoqgmmgipbmpk9dhsdcm73pe@4ax.com>
References: <20030821102627.C51705-100000@megazone.bigpanda.com>
	<25062.1061498540@sss.pgh.pa.us>
In-Reply-To: <25062.1061498540@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

On Thu, 21 Aug 2003 16:42:20 -0400, Tom Lane <tgl@sss.pgh.pa.us>
wrote:
>The point is that given
>	WHERE a = 1 OR b = 1
>you could create a plan that first indexscans on a, then indexscans on
>b --- but you mustn't return any tuples in the second scan that you
>already returned in the first.  IndexNext solves this by evaluating the
>prior-scan index conditions to see if they are true.

	WHERE a = 1 OR b = 2
and
	WHERE a = 1 OR a = 2

are totally different things.  In the latter case you don't have to
check prior conditions because the conditions are mutually exclusive.
Is this reasonably easy to find out at plan creation time?

Yes, I changed your example to make my point clear, because
	WHERE a = 1 OR a = 1
has its own set of problems.

Servus
 Manfred