mirror of
https://github.com/postgres/postgres.git
synced 2025-06-29 10:41:53 +03:00
8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef list
provided by Andrew.
This commit is contained in:
@ -8,7 +8,7 @@
|
||||
*
|
||||
*
|
||||
* IDENTIFICATION
|
||||
* $PostgreSQL: pgsql/src/backend/optimizer/path/joinpath.c,v 1.121 2009/02/05 01:24:55 tgl Exp $
|
||||
* $PostgreSQL: pgsql/src/backend/optimizer/path/joinpath.c,v 1.122 2009/06/11 14:48:59 momjian Exp $
|
||||
*
|
||||
*-------------------------------------------------------------------------
|
||||
*/
|
||||
@ -1022,14 +1022,14 @@ select_mergejoin_clauses(PlannerInfo *root,
|
||||
* Note: it would be bad if this condition failed for an otherwise
|
||||
* mergejoinable FULL JOIN clause, since that would result in
|
||||
* undesirable planner failure. I believe that is not possible
|
||||
* however; a variable involved in a full join could only appear
|
||||
* in below_outer_join eclasses, which aren't considered redundant.
|
||||
* however; a variable involved in a full join could only appear in
|
||||
* below_outer_join eclasses, which aren't considered redundant.
|
||||
*
|
||||
* This case *can* happen for left/right join clauses: the
|
||||
* outer-side variable could be equated to a constant. Because we
|
||||
* will propagate that constant across the join clause, the loss of
|
||||
* ability to do a mergejoin is not really all that big a deal, and
|
||||
* so it's not clear that improving this is important.
|
||||
* This case *can* happen for left/right join clauses: the outer-side
|
||||
* variable could be equated to a constant. Because we will propagate
|
||||
* that constant across the join clause, the loss of ability to do a
|
||||
* mergejoin is not really all that big a deal, and so it's not clear
|
||||
* that improving this is important.
|
||||
*/
|
||||
cache_mergeclause_eclasses(root, restrictinfo);
|
||||
|
||||
|
Reference in New Issue
Block a user