Tom Lane 6cb1c0238b Rewrite OR indexscan processing to be more flexible. We can now for the ... first time generate an OR indexscan for a two-column index when the WHERE condition is like 'col1 = foo AND (col2 = bar OR col2 = baz)' --- before, the OR had to be on the first column of the index or we'd not notice the possibility of using it. Some progress towards extracting OR indexscans from subclauses of an OR that references multiple relations, too, although this code is #ifdef'd out because it needs more work.		2004-01-04 00:07:32 +00:00
..
clauses.c	Adjust the definition of RestrictInfo's left_relids and right_relids	2003-12-30 23:53:15 +00:00
joininfo.c	$Header: -> $PostgreSQL Changes ...	2003-11-29 19:52:15 +00:00
Makefile	$Header: -> $PostgreSQL Changes ...	2003-11-29 19:52:15 +00:00
pathnode.c	$Header: -> $PostgreSQL Changes ...	2003-11-29 19:52:15 +00:00
plancat.c	Rewrite OR indexscan processing to be more flexible. We can now for the	2004-01-04 00:07:32 +00:00
relnode.c	Whole-row references were broken for subqueries and functions, because	2003-12-08 18:19:58 +00:00
restrictinfo.c	Rewrite OR indexscan processing to be more flexible. We can now for the	2004-01-04 00:07:32 +00:00
tlist.c	$Header: -> $PostgreSQL Changes ...	2003-11-29 19:52:15 +00:00
var.c	$Header: -> $PostgreSQL Changes ...	2003-11-29 19:52:15 +00:00