mirror of
https://github.com/postgres/postgres.git
synced 2025-07-28 23:42:10 +03:00
Add the ability to extract OR indexscan conditions from OR-of-AND
join conditions in which each OR subclause includes a constraint on the same relation. This implements the other useful side-effect of conversion to CNF format, without its unpleasant side-effects. As per pghackers discussion of a few weeks ago.
This commit is contained in:
@ -10,7 +10,7 @@
|
||||
*
|
||||
*
|
||||
* IDENTIFICATION
|
||||
* $PostgreSQL: pgsql/src/backend/optimizer/plan/createplan.c,v 1.161 2003/11/29 19:51:50 pgsql Exp $
|
||||
* $PostgreSQL: pgsql/src/backend/optimizer/plan/createplan.c,v 1.162 2004/01/05 05:07:35 tgl Exp $
|
||||
*
|
||||
*-------------------------------------------------------------------------
|
||||
*/
|
||||
@ -643,6 +643,7 @@ create_unique_plan(Query *root, UniquePath *best_path)
|
||||
plan = (Plan *) make_unique(my_tlist, plan, sortList);
|
||||
}
|
||||
|
||||
/* Adjust output size estimate (other fields should be OK already) */
|
||||
plan->plan_rows = best_path->rows;
|
||||
|
||||
return plan;
|
||||
|
Reference in New Issue
Block a user