1 /*-------------------------------------------------------------------------
4 * Definitions for planner's internal data structures.
7 * Portions Copyright (c) 1996-2006, PostgreSQL Global Development Group
8 * Portions Copyright (c) 1994, Regents of the University of California
10 * $PostgreSQL: pgsql/src/include/nodes/relation.h,v 1.128 2006/10/04 00:30:09 momjian Exp $
12 *-------------------------------------------------------------------------
17 #include "access/sdir.h"
18 #include "nodes/bitmapset.h"
19 #include "nodes/parsenodes.h"
20 #include "storage/block.h"
25 * Set of relation identifiers (indexes into the rangetable).
27 typedef Bitmapset *Relids;
30 * When looking for a "cheapest path", this enum specifies whether we want
31 * cheapest startup cost or cheapest total cost.
33 typedef enum CostSelector
35 STARTUP_COST, TOTAL_COST
39 * The cost estimate produced by cost_qual_eval() includes both a one-time
40 * (startup) cost, and a per-tuple cost.
42 typedef struct QualCost
44 Cost startup; /* one-time cost */
45 Cost per_tuple; /* per-evaluation cost */
51 * Per-query information for planning/optimization
53 * This struct is conventionally called "root" in all the planner routines.
54 * It holds links to all of the planner's working state, in addition to the
55 * original Query. Note that at present the planner extensively modifies
56 * the passed-in Query data structure; someday that should stop.
59 typedef struct PlannerInfo
63 Query *parse; /* the Query being planned */
66 * simple_rel_array holds pointers to "base rels" and "other rels" (see
67 * comments for RelOptInfo for more info). It is indexed by rangetable
68 * index (so entry 0 is always wasted). Entries can be NULL when an RTE
69 * does not correspond to a base relation, such as a join RTE or an
70 * unreferenced view RTE; or if the RelOptInfo hasn't been made yet.
72 struct RelOptInfo **simple_rel_array; /* All 1-relation RelOptInfos */
73 int simple_rel_array_size; /* allocated size of array */
76 * join_rel_list is a list of all join-relation RelOptInfos we have
77 * considered in this planning run. For small problems we just scan the
78 * list to do lookups, but when there are many join relations we build a
79 * hash table for faster lookups. The hash table is present and valid
80 * when join_rel_hash is not NULL. Note that we still maintain the list
81 * even when using the hash table for lookups; this simplifies life for
84 List *join_rel_list; /* list of join-relation RelOptInfos */
85 struct HTAB *join_rel_hash; /* optional hashtable for join relations */
87 List *equi_key_list; /* list of lists of equijoined PathKeyItems */
89 List *left_join_clauses; /* list of RestrictInfos for outer
90 * join clauses w/nonnullable var on
93 List *right_join_clauses; /* list of RestrictInfos for outer
94 * join clauses w/nonnullable var on
97 List *full_join_clauses; /* list of RestrictInfos for full
98 * outer join clauses */
100 List *oj_info_list; /* list of OuterJoinInfos */
102 List *in_info_list; /* list of InClauseInfos */
104 List *append_rel_list; /* list of AppendRelInfos */
106 List *query_pathkeys; /* desired pathkeys for query_planner(), and
107 * actual pathkeys afterwards */
109 List *group_pathkeys; /* groupClause pathkeys, if any */
110 List *sort_pathkeys; /* sortClause pathkeys, if any */
112 double total_table_pages; /* # of pages in all tables of query */
114 double tuple_fraction; /* tuple_fraction passed to query_planner */
116 bool hasJoinRTEs; /* true if any RTEs are RTE_JOIN kind */
117 bool hasOuterJoins; /* true if any RTEs are outer joins */
118 bool hasHavingQual; /* true if havingQual was non-null */
119 bool hasPseudoConstantQuals; /* true if any RestrictInfo has
120 * pseudoconstant = true */
126 * Per-relation information for planning/optimization
128 * For planning purposes, a "base rel" is either a plain relation (a table)
129 * or the output of a sub-SELECT or function that appears in the range table.
130 * In either case it is uniquely identified by an RT index. A "joinrel"
131 * is the joining of two or more base rels. A joinrel is identified by
132 * the set of RT indexes for its component baserels. We create RelOptInfo
133 * nodes for each baserel and joinrel, and store them in the PlannerInfo's
134 * simple_rel_array and join_rel_list respectively.
136 * Note that there is only one joinrel for any given set of component
137 * baserels, no matter what order we assemble them in; so an unordered
138 * set is the right datatype to identify it with.
140 * We also have "other rels", which are like base rels in that they refer to
141 * single RT indexes; but they are not part of the join tree, and are given
142 * a different RelOptKind to identify them.
144 * Currently the only kind of otherrels are those made for member relations
145 * of an "append relation", that is an inheritance set or UNION ALL subquery.
146 * An append relation has a parent RTE that is a base rel, which represents
147 * the entire append relation. The member RTEs are otherrels. The parent
148 * is present in the query join tree but the members are not. The member
149 * RTEs and otherrels are used to plan the scans of the individual tables or
150 * subqueries of the append set; then the parent baserel is given an Append
151 * plan comprising the best plans for the individual member rels. (See
152 * comments for AppendRelInfo for more information.)
154 * At one time we also made otherrels to represent join RTEs, for use in
155 * handling join alias Vars. Currently this is not needed because all join
156 * alias Vars are expanded to non-aliased form during preprocess_expression.
158 * Parts of this data structure are specific to various scan and join
159 * mechanisms. It didn't seem worth creating new node types for them.
161 * relids - Set of base-relation identifiers; it is a base relation
162 * if there is just one, a join relation if more than one
163 * rows - estimated number of tuples in the relation after restriction
164 * clauses have been applied (ie, output rows of a plan for it)
165 * width - avg. number of bytes per tuple in the relation after the
166 * appropriate projections have been done (ie, output width)
167 * reltargetlist - List of Var nodes for the attributes we need to
168 * output from this relation (in no particular order)
169 * NOTE: in a child relation, may contain RowExprs
170 * pathlist - List of Path nodes, one for each potentially useful
171 * method of generating the relation
172 * cheapest_startup_path - the pathlist member with lowest startup cost
173 * (regardless of its ordering)
174 * cheapest_total_path - the pathlist member with lowest total cost
175 * (regardless of its ordering)
176 * cheapest_unique_path - for caching cheapest path to produce unique
177 * (no duplicates) output from relation
179 * If the relation is a base relation it will have these fields set:
181 * relid - RTE index (this is redundant with the relids field, but
182 * is provided for convenience of access)
183 * rtekind - distinguishes plain relation, subquery, or function RTE
184 * min_attr, max_attr - range of valid AttrNumbers for rel
185 * attr_needed - array of bitmapsets indicating the highest joinrel
186 * in which each attribute is needed; if bit 0 is set then
187 * the attribute is needed as part of final targetlist
188 * attr_widths - cache space for per-attribute width estimates;
189 * zero means not computed yet
190 * indexlist - list of IndexOptInfo nodes for relation's indexes
191 * (always NIL if it's not a table)
192 * pages - number of disk pages in relation (zero if not a table)
193 * tuples - number of tuples in relation (not considering restrictions)
194 * subplan - plan for subquery (NULL if it's not a subquery)
196 * Note: for a subquery, tuples and subplan are not set immediately
197 * upon creation of the RelOptInfo object; they are filled in when
198 * set_base_rel_pathlist processes the object.
200 * For otherrels that are appendrel members, these fields are filled
201 * in just as for a baserel.
203 * The presence of the remaining fields depends on the restrictions
204 * and joins that the relation participates in:
206 * baserestrictinfo - List of RestrictInfo nodes, containing info about
207 * each non-join qualification clause in which this relation
208 * participates (only used for base rels)
209 * baserestrictcost - Estimated cost of evaluating the baserestrictinfo
210 * clauses at a single tuple (only used for base rels)
211 * joininfo - List of RestrictInfo nodes, containing info about each
212 * join clause in which this relation participates
213 * index_outer_relids - only used for base rels; set of outer relids
214 * that participate in indexable joinclauses for this rel
215 * index_inner_paths - only used for base rels; list of InnerIndexscanInfo
216 * nodes showing best indexpaths for various subsets of
217 * index_outer_relids.
219 * Note: Keeping a restrictinfo list in the RelOptInfo is useful only for
220 * base rels, because for a join rel the set of clauses that are treated as
221 * restrict clauses varies depending on which sub-relations we choose to join.
222 * (For example, in a 3-base-rel join, a clause relating rels 1 and 2 must be
223 * treated as a restrictclause if we join {1} and {2 3} to make {1 2 3}; but
224 * if we join {1 2} and {3} then that clause will be a restrictclause in {1 2}
225 * and should not be processed again at the level of {1 2 3}.) Therefore,
226 * the restrictinfo list in the join case appears in individual JoinPaths
227 * (field joinrestrictinfo), not in the parent relation. But it's OK for
228 * the RelOptInfo to store the joininfo list, because that is the same
229 * for a given rel no matter how we form it.
231 * We store baserestrictcost in the RelOptInfo (for base relations) because
232 * we know we will need it at least once (to price the sequential scan)
233 * and may need it multiple times to price index scans.
236 typedef enum RelOptKind
240 RELOPT_OTHER_MEMBER_REL
243 typedef struct RelOptInfo
247 RelOptKind reloptkind;
249 /* all relations included in this RelOptInfo */
250 Relids relids; /* set of base relids (rangetable indexes) */
252 /* size estimates generated by planner */
253 double rows; /* estimated number of result tuples */
254 int width; /* estimated avg width of result tuples */
256 /* materialization information */
257 List *reltargetlist; /* needed Vars */
258 List *pathlist; /* Path structures */
259 struct Path *cheapest_startup_path;
260 struct Path *cheapest_total_path;
261 struct Path *cheapest_unique_path;
263 /* information about a base rel (not set for join rels!) */
265 RTEKind rtekind; /* RELATION, SUBQUERY, or FUNCTION */
266 AttrNumber min_attr; /* smallest attrno of rel (often <0) */
267 AttrNumber max_attr; /* largest attrno of rel */
268 Relids *attr_needed; /* array indexed [min_attr .. max_attr] */
269 int32 *attr_widths; /* array indexed [min_attr .. max_attr] */
273 struct Plan *subplan; /* if subquery */
275 /* used by various scans and joins: */
276 List *baserestrictinfo; /* RestrictInfo structures (if base
278 QualCost baserestrictcost; /* cost of evaluating the above */
279 List *joininfo; /* RestrictInfo structures for join clauses
280 * involving this rel */
282 /* cached info about inner indexscan paths for relation: */
283 Relids index_outer_relids; /* other relids in indexable join
285 List *index_inner_paths; /* InnerIndexscanInfo nodes */
288 * Inner indexscans are not in the main pathlist because they are not
289 * usable except in specific join contexts. We use the index_inner_paths
290 * list just to avoid recomputing the best inner indexscan repeatedly for
291 * similar outer relations. See comments for InnerIndexscanInfo.
297 * Per-index information for planning/optimization
299 * Prior to Postgres 7.0, RelOptInfo was used to describe both relations
300 * and indexes, but that created confusion without actually doing anything
301 * useful. So now we have a separate IndexOptInfo struct for indexes.
303 * classlist[], indexkeys[], and ordering[] have ncolumns entries.
304 * Zeroes in the indexkeys[] array indicate index columns that are
305 * expressions; there is one element in indexprs for each such column.
307 * Note: for historical reasons, the classlist and ordering arrays have
308 * an extra entry that is always zero. Some code scans until it sees a
309 * zero entry, rather than looking at ncolumns.
311 * The indexprs and indpred expressions have been run through
312 * prepqual.c and eval_const_expressions() for ease of matching to
313 * WHERE clauses. indpred is in implicit-AND form.
316 typedef struct IndexOptInfo
320 Oid indexoid; /* OID of the index relation */
321 RelOptInfo *rel; /* back-link to index's table */
323 /* statistics from pg_class */
324 BlockNumber pages; /* number of disk pages in index */
325 double tuples; /* number of index tuples in index */
327 /* index descriptor information */
328 int ncolumns; /* number of columns in index */
329 Oid *classlist; /* OIDs of operator classes for columns */
330 int *indexkeys; /* column numbers of index's keys, or 0 */
331 Oid *ordering; /* OIDs of sort operators for each column */
332 Oid relam; /* OID of the access method (in pg_am) */
334 RegProcedure amcostestimate; /* OID of the access method's cost fcn */
336 List *indexprs; /* expressions for non-simple index columns */
337 List *indpred; /* predicate if a partial index, else NIL */
339 bool predOK; /* true if predicate matches query */
340 bool unique; /* true if a unique index */
341 bool amoptionalkey; /* can query omit key for the first column? */
348 * The sort ordering of a path is represented by a list of sublists of
349 * PathKeyItem nodes. An empty list implies no known ordering. Otherwise
350 * the first sublist represents the primary sort key, the second the
351 * first secondary sort key, etc. Each sublist contains one or more
352 * PathKeyItem nodes, each of which can be taken as the attribute that
353 * appears at that sort position. (See optimizer/README for more
357 typedef struct PathKeyItem
361 Node *key; /* the item that is ordered */
362 Oid sortop; /* the ordering operator ('<' op) */
365 * key typically points to a Var node, ie a relation attribute, but it can
366 * also point to an arbitrary expression representing the value indexed by
367 * an index expression.
372 * Type "Path" is used as-is for sequential-scan paths. For other
373 * path types it is the first component of a larger struct.
375 * Note: "pathtype" is the NodeTag of the Plan node we could build from this
376 * Path. It is partially redundant with the Path's NodeTag, but allows us
377 * to use the same Path type for multiple Plan types where there is no need
378 * to distinguish the Plan type during path processing.
385 NodeTag pathtype; /* tag identifying scan/join method */
387 RelOptInfo *parent; /* the relation this path can build */
389 /* estimated execution costs for path (see costsize.c for more info) */
390 Cost startup_cost; /* cost expended before fetching any tuples */
391 Cost total_cost; /* total cost (assuming all tuples fetched) */
393 List *pathkeys; /* sort ordering of path's output */
394 /* pathkeys is a List of Lists of PathKeyItem nodes; see above */
398 * IndexPath represents an index scan over a single index.
400 * 'indexinfo' is the index to be scanned.
402 * 'indexclauses' is a list of index qualification clauses, with implicit
403 * AND semantics across the list. Each clause is a RestrictInfo node from
404 * the query's WHERE or JOIN conditions.
406 * 'indexquals' has the same structure as 'indexclauses', but it contains
407 * the actual indexqual conditions that can be used with the index.
408 * In simple cases this is identical to 'indexclauses', but when special
409 * indexable operators appear in 'indexclauses', they are replaced by the
410 * derived indexscannable conditions in 'indexquals'.
412 * 'isjoininner' is TRUE if the path is a nestloop inner scan (that is,
413 * some of the index conditions are join rather than restriction clauses).
414 * Note that the path costs will be calculated differently from a plain
415 * indexscan in this case, and in addition there's a special 'rows' value
416 * different from the parent RelOptInfo's (see below).
418 * 'indexscandir' is one of:
419 * ForwardScanDirection: forward scan of an ordered index
420 * BackwardScanDirection: backward scan of an ordered index
421 * NoMovementScanDirection: scan of an unordered index, or don't care
422 * (The executor doesn't care whether it gets ForwardScanDirection or
423 * NoMovementScanDirection for an indexscan, but the planner wants to
424 * distinguish ordered from unordered indexes for building pathkeys.)
426 * 'indextotalcost' and 'indexselectivity' are saved in the IndexPath so that
427 * we need not recompute them when considering using the same index in a
428 * bitmap index/heap scan (see BitmapHeapPath). The costs of the IndexPath
429 * itself represent the costs of an IndexScan plan type.
431 * 'rows' is the estimated result tuple count for the indexscan. This
432 * is the same as path.parent->rows for a simple indexscan, but it is
433 * different for a nestloop inner scan, because the additional indexquals
434 * coming from join clauses make the scan more selective than the parent
435 * rel's restrict clauses alone would do.
438 typedef struct IndexPath
441 IndexOptInfo *indexinfo;
445 ScanDirection indexscandir;
447 Selectivity indexselectivity;
448 double rows; /* estimated number of result tuples */
452 * BitmapHeapPath represents one or more indexscans that generate TID bitmaps
453 * instead of directly accessing the heap, followed by AND/OR combinations
454 * to produce a single bitmap, followed by a heap scan that uses the bitmap.
455 * Note that the output is always considered unordered, since it will come
456 * out in physical heap order no matter what the underlying indexes did.
458 * The individual indexscans are represented by IndexPath nodes, and any
459 * logic on top of them is represented by a tree of BitmapAndPath and
460 * BitmapOrPath nodes. Notice that we can use the same IndexPath node both
461 * to represent a regular IndexScan plan, and as the child of a BitmapHeapPath
462 * that represents scanning the same index using a BitmapIndexScan. The
463 * startup_cost and total_cost figures of an IndexPath always represent the
464 * costs to use it as a regular IndexScan. The costs of a BitmapIndexScan
465 * can be computed using the IndexPath's indextotalcost and indexselectivity.
467 * BitmapHeapPaths can be nestloop inner indexscans. The isjoininner and
468 * rows fields serve the same purpose as for plain IndexPaths.
470 typedef struct BitmapHeapPath
473 Path *bitmapqual; /* IndexPath, BitmapAndPath, BitmapOrPath */
474 bool isjoininner; /* T if it's a nestloop inner scan */
475 double rows; /* estimated number of result tuples */
479 * BitmapAndPath represents a BitmapAnd plan node; it can only appear as
480 * part of the substructure of a BitmapHeapPath. The Path structure is
481 * a bit more heavyweight than we really need for this, but for simplicity
482 * we make it a derivative of Path anyway.
484 typedef struct BitmapAndPath
487 List *bitmapquals; /* IndexPaths and BitmapOrPaths */
488 Selectivity bitmapselectivity;
492 * BitmapOrPath represents a BitmapOr plan node; it can only appear as
493 * part of the substructure of a BitmapHeapPath. The Path structure is
494 * a bit more heavyweight than we really need for this, but for simplicity
495 * we make it a derivative of Path anyway.
497 typedef struct BitmapOrPath
500 List *bitmapquals; /* IndexPaths and BitmapAndPaths */
501 Selectivity bitmapselectivity;
505 * TidPath represents a scan by TID
507 * tidquals is an implicitly OR'ed list of qual expressions of the form
508 * "CTID = pseudoconstant" or "CTID = ANY(pseudoconstant_array)".
509 * Note they are bare expressions, not RestrictInfos.
511 typedef struct TidPath
514 List *tidquals; /* qual(s) involving CTID = something */
518 * AppendPath represents an Append plan, ie, successive execution of
519 * several member plans.
521 * Note: it is possible for "subpaths" to contain only one, or even no,
522 * elements. These cases are optimized during create_append_plan.
524 typedef struct AppendPath
527 List *subpaths; /* list of component Paths */
531 * ResultPath represents use of a Result plan node to compute a variable-free
532 * targetlist with no underlying tables (a "SELECT expressions" query).
533 * The query could have a WHERE clause, too, represented by "quals".
535 * Note that quals is a list of bare clauses, not RestrictInfos.
537 typedef struct ResultPath
544 * MaterialPath represents use of a Material plan node, i.e., caching of
545 * the output of its subpath. This is used when the subpath is expensive
546 * and needs to be scanned repeatedly, or when we need mark/restore ability
547 * and the subpath doesn't have it.
549 typedef struct MaterialPath
556 * UniquePath represents elimination of distinct rows from the output of
559 * This is unlike the other Path nodes in that it can actually generate
560 * different plans: either hash-based or sort-based implementation, or a
561 * no-op if the input path can be proven distinct already. The decision
562 * is sufficiently localized that it's not worth having separate Path node
563 * types. (Note: in the no-op case, we could eliminate the UniquePath node
564 * entirely and just return the subpath; but it's convenient to have a
565 * UniquePath in the path tree to signal upper-level routines that the input
566 * is known distinct.)
570 UNIQUE_PATH_NOOP, /* input is known unique already */
571 UNIQUE_PATH_HASH, /* use hashing */
572 UNIQUE_PATH_SORT /* use sorting */
575 typedef struct UniquePath
579 UniquePathMethod umethod;
580 double rows; /* estimated number of result tuples */
584 * All join-type paths share these fields.
587 typedef struct JoinPath
593 Path *outerjoinpath; /* path for the outer side of the join */
594 Path *innerjoinpath; /* path for the inner side of the join */
596 List *joinrestrictinfo; /* RestrictInfos to apply to join */
599 * See the notes for RelOptInfo to understand why joinrestrictinfo is
600 * needed in JoinPath, and can't be merged into the parent RelOptInfo.
605 * A nested-loop path needs no special fields.
608 typedef JoinPath NestPath;
611 * A mergejoin path has these fields.
613 * path_mergeclauses lists the clauses (in the form of RestrictInfos)
614 * that will be used in the merge.
616 * Note that the mergeclauses are a subset of the parent relation's
617 * restriction-clause list. Any join clauses that are not mergejoinable
618 * appear only in the parent's restrict list, and must be checked by a
619 * qpqual at execution time.
621 * outersortkeys (resp. innersortkeys) is NIL if the outer path
622 * (resp. inner path) is already ordered appropriately for the
623 * mergejoin. If it is not NIL then it is a PathKeys list describing
624 * the ordering that must be created by an explicit sort step.
627 typedef struct MergePath
630 List *path_mergeclauses; /* join clauses to be used for merge */
631 List *outersortkeys; /* keys for explicit sort, if any */
632 List *innersortkeys; /* keys for explicit sort, if any */
636 * A hashjoin path has these fields.
638 * The remarks above for mergeclauses apply for hashclauses as well.
640 * Hashjoin does not care what order its inputs appear in, so we have
641 * no need for sortkeys.
644 typedef struct HashPath
647 List *path_hashclauses; /* join clauses used for hashing */
651 * Restriction clause info.
653 * We create one of these for each AND sub-clause of a restriction condition
654 * (WHERE or JOIN/ON clause). Since the restriction clauses are logically
655 * ANDed, we can use any one of them or any subset of them to filter out
656 * tuples, without having to evaluate the rest. The RestrictInfo node itself
657 * stores data used by the optimizer while choosing the best query plan.
659 * If a restriction clause references a single base relation, it will appear
660 * in the baserestrictinfo list of the RelOptInfo for that base rel.
662 * If a restriction clause references more than one base rel, it will
663 * appear in the joininfo list of every RelOptInfo that describes a strict
664 * subset of the base rels mentioned in the clause. The joininfo lists are
665 * used to drive join tree building by selecting plausible join candidates.
666 * The clause cannot actually be applied until we have built a join rel
667 * containing all the base rels it references, however.
669 * When we construct a join rel that includes all the base rels referenced
670 * in a multi-relation restriction clause, we place that clause into the
671 * joinrestrictinfo lists of paths for the join rel, if neither left nor
672 * right sub-path includes all base rels referenced in the clause. The clause
673 * will be applied at that join level, and will not propagate any further up
674 * the join tree. (Note: the "predicate migration" code was once intended to
675 * push restriction clauses up and down the plan tree based on evaluation
676 * costs, but it's dead code and is unlikely to be resurrected in the
677 * foreseeable future.)
679 * Note that in the presence of more than two rels, a multi-rel restriction
680 * might reach different heights in the join tree depending on the join
681 * sequence we use. So, these clauses cannot be associated directly with
682 * the join RelOptInfo, but must be kept track of on a per-join-path basis.
684 * When dealing with outer joins we have to be very careful about pushing qual
685 * clauses up and down the tree. An outer join's own JOIN/ON conditions must
686 * be evaluated exactly at that join node, and any quals appearing in WHERE or
687 * in a JOIN above the outer join cannot be pushed down below the outer join.
688 * Otherwise the outer join will produce wrong results because it will see the
689 * wrong sets of input rows. All quals are stored as RestrictInfo nodes
690 * during planning, but there's a flag to indicate whether a qual has been
691 * pushed down to a lower level than its original syntactic placement in the
692 * join tree would suggest. If an outer join prevents us from pushing a qual
693 * down to its "natural" semantic level (the level associated with just the
694 * base rels used in the qual) then we mark the qual with a "required_relids"
695 * value including more than just the base rels it actually uses. By
696 * pretending that the qual references all the rels appearing in the outer
697 * join, we prevent it from being evaluated below the outer join's joinrel.
698 * When we do form the outer join's joinrel, we still need to distinguish
699 * those quals that are actually in that join's JOIN/ON condition from those
700 * that appeared higher in the tree and were pushed down to the join rel
701 * because they used no other rels. That's what the is_pushed_down flag is
702 * for; it tells us that a qual came from a point above the join of the
703 * set of base rels listed in required_relids. A clause that originally came
704 * from WHERE will *always* have its is_pushed_down flag set; a clause that
705 * came from an INNER JOIN condition, but doesn't use all the rels being
706 * joined, will also have is_pushed_down set because it will get attached to
707 * some lower joinrel.
709 * When application of a qual must be delayed by outer join, we also mark it
710 * with outerjoin_delayed = true. This isn't redundant with required_relids
711 * because that might equal clause_relids whether or not it's an outer-join
714 * In general, the referenced clause might be arbitrarily complex. The
715 * kinds of clauses we can handle as indexscan quals, mergejoin clauses,
716 * or hashjoin clauses are fairly limited --- the code for each kind of
717 * path is responsible for identifying the restrict clauses it can use
718 * and ignoring the rest. Clauses not implemented by an indexscan,
719 * mergejoin, or hashjoin will be placed in the plan qual or joinqual field
720 * of the finished Plan node, where they will be enforced by general-purpose
721 * qual-expression-evaluation code. (But we are still entitled to count
722 * their selectivity when estimating the result tuple count, if we
723 * can guess what it is...)
725 * When the referenced clause is an OR clause, we generate a modified copy
726 * in which additional RestrictInfo nodes are inserted below the top-level
727 * OR/AND structure. This is a convenience for OR indexscan processing:
728 * indexquals taken from either the top level or an OR subclause will have
729 * associated RestrictInfo nodes.
731 * The can_join flag is set true if the clause looks potentially useful as
732 * a merge or hash join clause, that is if it is a binary opclause with
733 * nonoverlapping sets of relids referenced in the left and right sides.
734 * (Whether the operator is actually merge or hash joinable isn't checked,
737 * The pseudoconstant flag is set true if the clause contains no Vars of
738 * the current query level and no volatile functions. Such a clause can be
739 * pulled out and used as a one-time qual in a gating Result node. We keep
740 * pseudoconstant clauses in the same lists as other RestrictInfos so that
741 * the regular clause-pushing machinery can assign them to the correct join
742 * level, but they need to be treated specially for cost and selectivity
743 * estimates. Note that a pseudoconstant clause can never be an indexqual
744 * or merge or hash join clause, so it's of no interest to large parts of
748 typedef struct RestrictInfo
752 Expr *clause; /* the represented clause of WHERE or JOIN */
754 bool is_pushed_down; /* TRUE if clause was pushed down in level */
756 bool outerjoin_delayed; /* TRUE if delayed by outer join */
758 bool can_join; /* see comment above */
760 bool pseudoconstant; /* see comment above */
762 /* The set of relids (varnos) actually referenced in the clause: */
763 Relids clause_relids;
765 /* The set of relids required to evaluate the clause: */
766 Relids required_relids;
768 /* These fields are set for any binary opclause: */
769 Relids left_relids; /* relids in left side of clause */
770 Relids right_relids; /* relids in right side of clause */
772 /* This field is NULL unless clause is an OR clause: */
773 Expr *orclause; /* modified clause with RestrictInfos */
775 /* cache space for cost and selectivity */
776 QualCost eval_cost; /* eval cost of clause; -1 if not yet set */
777 Selectivity this_selec; /* selectivity; -1 if not yet set */
779 /* valid if clause is mergejoinable, else InvalidOid: */
780 Oid mergejoinoperator; /* copy of clause operator */
781 Oid left_sortop; /* leftside sortop needed for mergejoin */
782 Oid right_sortop; /* rightside sortop needed for mergejoin */
784 /* cache space for mergeclause processing; NIL if not yet set */
785 List *left_pathkey; /* canonical pathkey for left side */
786 List *right_pathkey; /* canonical pathkey for right side */
788 /* cache space for mergeclause processing; -1 if not yet set */
789 Selectivity left_mergescansel; /* fraction of left side to scan */
790 Selectivity right_mergescansel; /* fraction of right side to scan */
792 /* valid if clause is hashjoinable, else InvalidOid: */
793 Oid hashjoinoperator; /* copy of clause operator */
795 /* cache space for hashclause processing; -1 if not yet set */
796 Selectivity left_bucketsize; /* avg bucketsize of left side */
797 Selectivity right_bucketsize; /* avg bucketsize of right side */
801 * Inner indexscan info.
803 * An inner indexscan is one that uses one or more joinclauses as index
804 * conditions (perhaps in addition to plain restriction clauses). So it
805 * can only be used as the inner path of a nestloop join where the outer
806 * relation includes all other relids appearing in those joinclauses.
807 * The set of usable joinclauses, and thus the best inner indexscan,
808 * thus varies depending on which outer relation we consider; so we have
809 * to recompute the best such path for every join. To avoid lots of
810 * redundant computation, we cache the results of such searches. For
811 * each relation we compute the set of possible otherrelids (all relids
812 * appearing in joinquals that could become indexquals for this table).
813 * Two outer relations whose relids have the same intersection with this
814 * set will have the same set of available joinclauses and thus the same
815 * best inner indexscan for the inner relation. By taking the intersection
816 * before scanning the cache, we avoid recomputing when considering
817 * join rels that differ only by the inclusion of irrelevant other rels.
819 * The search key also includes a bool showing whether the join being
820 * considered is an outer join. Since we constrain the join order for
821 * outer joins, I believe that this bool can only have one possible value
822 * for any particular base relation; but store it anyway to avoid confusion.
825 typedef struct InnerIndexscanInfo
828 /* The lookup key: */
829 Relids other_relids; /* a set of relevant other relids */
830 bool isouterjoin; /* true if join is outer */
831 /* Best path for this lookup key: */
832 Path *best_innerpath; /* best inner indexscan, or NULL if none */
833 } InnerIndexscanInfo;
838 * One-sided outer joins constrain the order of joining partially but not
839 * completely. We flatten such joins into the planner's top-level list of
840 * relations to join, but record information about each outer join in an
841 * OuterJoinInfo struct. These structs are kept in the PlannerInfo node's
844 * min_lefthand and min_righthand are the sets of base relids that must be
845 * available on each side when performing the outer join. lhs_strict is
846 * true if the outer join's condition cannot succeed when the LHS variables
847 * are all NULL (this means that the outer join can commute with upper-level
848 * outer joins even if it appears in their RHS). We don't bother to set
849 * lhs_strict for FULL JOINs, however.
851 * It is not valid for either min_lefthand or min_righthand to be empty sets;
852 * if they were, this would break the logic that enforces join order.
854 * Note: OuterJoinInfo directly represents only LEFT JOIN and FULL JOIN;
855 * RIGHT JOIN is handled by switching the inputs to make it a LEFT JOIN.
856 * We make an OuterJoinInfo for FULL JOINs even though there is no flexibility
857 * of planning for them, because this simplifies make_join_rel()'s API.
860 typedef struct OuterJoinInfo
863 Relids min_lefthand; /* base relids in minimum LHS for join */
864 Relids min_righthand; /* base relids in minimum RHS for join */
865 bool is_full_join; /* it's a FULL OUTER JOIN */
866 bool lhs_strict; /* joinclause is strict for some LHS rel */
872 * When we convert top-level IN quals into join operations, we must restrict
873 * the order of joining and use special join methods at some join points.
874 * We record information about each such IN clause in an InClauseInfo struct.
875 * These structs are kept in the PlannerInfo node's in_info_list.
878 typedef struct InClauseInfo
881 Relids lefthand; /* base relids in lefthand expressions */
882 Relids righthand; /* base relids coming from the subselect */
883 List *sub_targetlist; /* targetlist of original RHS subquery */
886 * Note: sub_targetlist is just a list of Vars or expressions; it does not
887 * contain TargetEntry nodes.
892 * Append-relation info.
894 * When we expand an inheritable table or a UNION-ALL subselect into an
895 * "append relation" (essentially, a list of child RTEs), we build an
896 * AppendRelInfo for each child RTE. The list of AppendRelInfos indicates
897 * which child RTEs must be included when expanding the parent, and each
898 * node carries information needed to translate Vars referencing the parent
899 * into Vars referencing that child.
901 * These structs are kept in the PlannerInfo node's append_rel_list.
902 * Note that we just throw all the structs into one list, and scan the
903 * whole list when desiring to expand any one parent. We could have used
904 * a more complex data structure (eg, one list per parent), but this would
905 * be harder to update during operations such as pulling up subqueries,
906 * and not really any easier to scan. Considering that typical queries
907 * will not have many different append parents, it doesn't seem worthwhile
908 * to complicate things.
910 * Note: after completion of the planner prep phase, any given RTE is an
911 * append parent having entries in append_rel_list if and only if its
912 * "inh" flag is set. We clear "inh" for plain tables that turn out not
913 * to have inheritance children, and (in an abuse of the original meaning
914 * of the flag) we set "inh" for subquery RTEs that turn out to be
915 * flattenable UNION ALL queries. This lets us avoid useless searches
916 * of append_rel_list.
918 * Note: the data structure assumes that append-rel members are single
919 * baserels. This is OK for inheritance, but it prevents us from pulling
920 * up a UNION ALL member subquery if it contains a join. While that could
921 * be fixed with a more complex data structure, at present there's not much
922 * point because no improvement in the plan could result.
925 typedef struct AppendRelInfo
930 * These fields uniquely identify this append relationship. There can be
931 * (in fact, always should be) multiple AppendRelInfos for the same
932 * parent_relid, but never more than one per child_relid, since a given
933 * RTE cannot be a child of more than one append parent.
935 Index parent_relid; /* RT index of append parent rel */
936 Index child_relid; /* RT index of append child rel */
939 * For an inheritance appendrel, the parent and child are both regular
940 * relations, and we store their rowtype OIDs here for use in translating
941 * whole-row Vars. For a UNION-ALL appendrel, the parent and child are
942 * both subqueries with no named rowtype, and we store InvalidOid here.
944 Oid parent_reltype; /* OID of parent's composite type */
945 Oid child_reltype; /* OID of child's composite type */
948 * The N'th element of this list is the integer column number of the child
949 * column corresponding to the N'th column of the parent. A list element
950 * is zero if it corresponds to a dropped column of the parent (this is
951 * only possible for inheritance cases, not UNION ALL).
953 List *col_mappings; /* list of child attribute numbers */
956 * The N'th element of this list is a Var or expression representing the
957 * child column corresponding to the N'th column of the parent. This is
958 * used to translate Vars referencing the parent rel into references to
959 * the child. A list element is NULL if it corresponds to a dropped
960 * column of the parent (this is only possible for inheritance cases, not
963 * This might seem redundant with the col_mappings data, but it is handy
964 * because flattening of sub-SELECTs that are members of a UNION ALL will
965 * cause changes in the expressions that need to be substituted for a
966 * parent Var. Adjusting this data structure lets us track what really
967 * needs to be substituted.
969 * Notice we only store entries for user columns (attno > 0). Whole-row
970 * Vars are special-cased, and system columns (attno < 0) need no special
971 * translation since their attnos are the same for all tables.
973 * Caution: the Vars have varlevelsup = 0. Be careful to adjust as needed
974 * when copying into a subquery.
976 List *translated_vars; /* Expressions in the child's Vars */
979 * We store the parent table's OID here for inheritance, or InvalidOid for
980 * UNION ALL. This is only needed to help in generating error messages if
981 * an attempt is made to reference a dropped parent column.
983 Oid parent_reloid; /* OID of parent relation */
986 #endif /* RELATION_H */