Tom Lane 953208a34c In a nestloop inner indexscan, it's OK to use pushed-down baserestrictinfo ... clauses even if it's an outer join. This is a corner case since such clauses could only arise from weird OUTER JOIN ON conditions, but worth fixing. Per example from Ron at cheapcomplexdevices.com.		2005-12-06 16:50:36 +00:00
..
allpaths.c	Re-run pgindent, fixing a problem where comment lines after a blank	2005-11-22 18:17:34 +00:00
clausesel.c	Teach planner and executor to handle ScalarArrayOpExpr as an indexable	2005-11-25 19:47:50 +00:00
costsize.c	Teach tid-scan code to make use of "ctid = ANY (array)" clauses, so that	2005-11-26 22:14:57 +00:00
indxpath.c	In a nestloop inner indexscan, it's OK to use pushed-down baserestrictinfo	2005-12-06 16:50:36 +00:00
joinpath.c	Re-run pgindent, fixing a problem where comment lines after a blank	2005-11-22 18:17:34 +00:00
joinrels.c	Re-run pgindent, fixing a problem where comment lines after a blank	2005-11-22 18:17:34 +00:00
Makefile	$Header: -> $PostgreSQL Changes ...	2003-11-29 19:52:15 +00:00
orindxpath.c	Re-run pgindent, fixing a problem where comment lines after a blank	2005-11-22 18:17:34 +00:00
pathkeys.c	Re-run pgindent, fixing a problem where comment lines after a blank	2005-11-22 18:17:34 +00:00
tidpath.c	Teach tid-scan code to make use of "ctid = ANY (array)" clauses, so that	2005-11-26 22:14:57 +00:00