1 /*-------------------------------------------------------------------------
4 * Definitions for planner's internal data structures.
7 * Portions Copyright (c) 1996-2008, 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.162 2008/10/21 20:42:53 tgl Exp $
12 *-------------------------------------------------------------------------
17 #include "access/sdir.h"
18 #include "nodes/bitmapset.h"
19 #include "nodes/params.h"
20 #include "nodes/parsenodes.h"
21 #include "storage/block.h"
26 * Set of relation identifiers (indexes into the rangetable).
28 typedef Bitmapset *Relids;
31 * When looking for a "cheapest path", this enum specifies whether we want
32 * cheapest startup cost or cheapest total cost.
34 typedef enum CostSelector
36 STARTUP_COST, TOTAL_COST
40 * The cost estimate produced by cost_qual_eval() includes both a one-time
41 * (startup) cost, and a per-tuple cost.
43 typedef struct QualCost
45 Cost startup; /* one-time cost */
46 Cost per_tuple; /* per-evaluation cost */
52 * Global information for planning/optimization
54 * PlannerGlobal holds state for an entire planner invocation; this state
55 * is shared across all levels of sub-Queries that exist in the command being
59 typedef struct PlannerGlobal
63 ParamListInfo boundParams; /* Param values provided to planner() */
65 List *paramlist; /* to keep track of cross-level Params */
67 List *subplans; /* Plans for SubPlan nodes */
69 List *subrtables; /* Rangetables for SubPlan nodes */
71 Bitmapset *rewindPlanIDs; /* indices of subplans that require REWIND */
73 List *finalrtable; /* "flat" rangetable for executor */
75 List *relationOids; /* OIDs of relations the plan depends on */
77 List *invalItems; /* other dependencies, as PlanInvalItems */
79 Index lastPHId; /* highest PlaceHolderVar ID assigned */
81 bool transientPlan; /* redo plan when TransactionXmin changes? */
84 /* macro for fetching the Plan associated with a SubPlan node */
85 #define planner_subplan_get_plan(root, subplan) \
86 ((Plan *) list_nth((root)->glob->subplans, (subplan)->plan_id - 1))
91 * Per-query information for planning/optimization
93 * This struct is conventionally called "root" in all the planner routines.
94 * It holds links to all of the planner's working state, in addition to the
95 * original Query. Note that at present the planner extensively modifies
96 * the passed-in Query data structure; someday that should stop.
99 typedef struct PlannerInfo
103 Query *parse; /* the Query being planned */
105 PlannerGlobal *glob; /* global info for current planner run */
107 Index query_level; /* 1 at the outermost Query */
109 struct PlannerInfo *parent_root; /* NULL at outermost Query */
112 * simple_rel_array holds pointers to "base rels" and "other rels" (see
113 * comments for RelOptInfo for more info). It is indexed by rangetable
114 * index (so entry 0 is always wasted). Entries can be NULL when an RTE
115 * does not correspond to a base relation, such as a join RTE or an
116 * unreferenced view RTE; or if the RelOptInfo hasn't been made yet.
118 struct RelOptInfo **simple_rel_array; /* All 1-rel RelOptInfos */
119 int simple_rel_array_size; /* allocated size of array */
122 * simple_rte_array is the same length as simple_rel_array and holds
123 * pointers to the associated rangetable entries. This lets us avoid
124 * rt_fetch(), which can be a bit slow once large inheritance sets have
127 RangeTblEntry **simple_rte_array; /* rangetable as an array */
130 * join_rel_list is a list of all join-relation RelOptInfos we have
131 * considered in this planning run. For small problems we just scan the
132 * list to do lookups, but when there are many join relations we build a
133 * hash table for faster lookups. The hash table is present and valid
134 * when join_rel_hash is not NULL. Note that we still maintain the list
135 * even when using the hash table for lookups; this simplifies life for
138 List *join_rel_list; /* list of join-relation RelOptInfos */
139 struct HTAB *join_rel_hash; /* optional hashtable for join relations */
141 List *resultRelations; /* integer list of RT indexes, or NIL */
143 List *returningLists; /* list of lists of TargetEntry, or NIL */
145 List *init_plans; /* init SubPlans for query */
147 List *cte_plan_ids; /* per-CTE-item list of subplan IDs */
149 List *eq_classes; /* list of active EquivalenceClasses */
151 List *canon_pathkeys; /* list of "canonical" PathKeys */
153 List *left_join_clauses; /* list of RestrictInfos for
154 * mergejoinable outer join clauses
155 * w/nonnullable var on left */
157 List *right_join_clauses; /* list of RestrictInfos for
158 * mergejoinable outer join clauses
159 * w/nonnullable var on right */
161 List *full_join_clauses; /* list of RestrictInfos for
162 * mergejoinable full join clauses */
164 List *join_info_list; /* list of SpecialJoinInfos */
166 List *append_rel_list; /* list of AppendRelInfos */
168 List *placeholder_list; /* list of PlaceHolderInfos */
170 List *query_pathkeys; /* desired pathkeys for query_planner(), and
171 * actual pathkeys afterwards */
173 List *group_pathkeys; /* groupClause pathkeys, if any */
174 List *distinct_pathkeys; /* distinctClause pathkeys, if any */
175 List *sort_pathkeys; /* sortClause pathkeys, if any */
177 List *initial_rels; /* RelOptInfos we are now trying to join */
179 MemoryContext planner_cxt; /* context holding PlannerInfo */
181 double total_table_pages; /* # of pages in all tables of query */
183 double tuple_fraction; /* tuple_fraction passed to query_planner */
185 bool hasJoinRTEs; /* true if any RTEs are RTE_JOIN kind */
186 bool hasHavingQual; /* true if havingQual was non-null */
187 bool hasPseudoConstantQuals; /* true if any RestrictInfo has
188 * pseudoconstant = true */
189 bool hasRecursion; /* true if planning a recursive WITH item */
191 /* These fields are used only when hasRecursion is true: */
192 int wt_param_id; /* PARAM_EXEC ID for the work table */
193 struct Plan *non_recursive_plan; /* plan for non-recursive term */
198 * In places where it's known that simple_rte_array[] must have been prepared
199 * already, we just index into it to fetch RTEs. In code that might be
200 * executed before or after entering query_planner(), use this macro.
202 #define planner_rt_fetch(rti, root) \
203 ((root)->simple_rte_array ? (root)->simple_rte_array[rti] : \
204 rt_fetch(rti, (root)->parse->rtable))
209 * Per-relation information for planning/optimization
211 * For planning purposes, a "base rel" is either a plain relation (a table)
212 * or the output of a sub-SELECT or function that appears in the range table.
213 * In either case it is uniquely identified by an RT index. A "joinrel"
214 * is the joining of two or more base rels. A joinrel is identified by
215 * the set of RT indexes for its component baserels. We create RelOptInfo
216 * nodes for each baserel and joinrel, and store them in the PlannerInfo's
217 * simple_rel_array and join_rel_list respectively.
219 * Note that there is only one joinrel for any given set of component
220 * baserels, no matter what order we assemble them in; so an unordered
221 * set is the right datatype to identify it with.
223 * We also have "other rels", which are like base rels in that they refer to
224 * single RT indexes; but they are not part of the join tree, and are given
225 * a different RelOptKind to identify them.
227 * Currently the only kind of otherrels are those made for member relations
228 * of an "append relation", that is an inheritance set or UNION ALL subquery.
229 * An append relation has a parent RTE that is a base rel, which represents
230 * the entire append relation. The member RTEs are otherrels. The parent
231 * is present in the query join tree but the members are not. The member
232 * RTEs and otherrels are used to plan the scans of the individual tables or
233 * subqueries of the append set; then the parent baserel is given an Append
234 * plan comprising the best plans for the individual member rels. (See
235 * comments for AppendRelInfo for more information.)
237 * At one time we also made otherrels to represent join RTEs, for use in
238 * handling join alias Vars. Currently this is not needed because all join
239 * alias Vars are expanded to non-aliased form during preprocess_expression.
241 * Parts of this data structure are specific to various scan and join
242 * mechanisms. It didn't seem worth creating new node types for them.
244 * relids - Set of base-relation identifiers; it is a base relation
245 * if there is just one, a join relation if more than one
246 * rows - estimated number of tuples in the relation after restriction
247 * clauses have been applied (ie, output rows of a plan for it)
248 * width - avg. number of bytes per tuple in the relation after the
249 * appropriate projections have been done (ie, output width)
250 * reltargetlist - List of Var and PlaceHolderVar nodes for the values
251 * we need to output from this relation.
252 * List is in no particular order, but all rels of an
253 * appendrel set must use corresponding orders.
254 * NOTE: in a child relation, may contain RowExpr or
255 * ConvertRowtypeExpr representing a whole-row Var.
256 * pathlist - List of Path nodes, one for each potentially useful
257 * method of generating the relation
258 * cheapest_startup_path - the pathlist member with lowest startup cost
259 * (regardless of its ordering)
260 * cheapest_total_path - the pathlist member with lowest total cost
261 * (regardless of its ordering)
262 * cheapest_unique_path - for caching cheapest path to produce unique
263 * (no duplicates) output from relation
265 * If the relation is a base relation it will have these fields set:
267 * relid - RTE index (this is redundant with the relids field, but
268 * is provided for convenience of access)
269 * rtekind - distinguishes plain relation, subquery, or function RTE
270 * min_attr, max_attr - range of valid AttrNumbers for rel
271 * attr_needed - array of bitmapsets indicating the highest joinrel
272 * in which each attribute is needed; if bit 0 is set then
273 * the attribute is needed as part of final targetlist
274 * attr_widths - cache space for per-attribute width estimates;
275 * zero means not computed yet
276 * indexlist - list of IndexOptInfo nodes for relation's indexes
277 * (always NIL if it's not a table)
278 * pages - number of disk pages in relation (zero if not a table)
279 * tuples - number of tuples in relation (not considering restrictions)
280 * subplan - plan for subquery (NULL if it's not a subquery)
281 * subrtable - rangetable for subquery (NIL if it's not a subquery)
283 * Note: for a subquery, tuples and subplan are not set immediately
284 * upon creation of the RelOptInfo object; they are filled in when
285 * set_base_rel_pathlist processes the object.
287 * For otherrels that are appendrel members, these fields are filled
288 * in just as for a baserel.
290 * The presence of the remaining fields depends on the restrictions
291 * and joins that the relation participates in:
293 * baserestrictinfo - List of RestrictInfo nodes, containing info about
294 * each non-join qualification clause in which this relation
295 * participates (only used for base rels)
296 * baserestrictcost - Estimated cost of evaluating the baserestrictinfo
297 * clauses at a single tuple (only used for base rels)
298 * joininfo - List of RestrictInfo nodes, containing info about each
299 * join clause in which this relation participates (but
300 * note this excludes clauses that might be derivable from
301 * EquivalenceClasses)
302 * has_eclass_joins - flag that EquivalenceClass joins are possible
303 * index_outer_relids - only used for base rels; set of outer relids
304 * that participate in indexable joinclauses for this rel
305 * index_inner_paths - only used for base rels; list of InnerIndexscanInfo
306 * nodes showing best indexpaths for various subsets of
307 * index_outer_relids.
309 * Note: Keeping a restrictinfo list in the RelOptInfo is useful only for
310 * base rels, because for a join rel the set of clauses that are treated as
311 * restrict clauses varies depending on which sub-relations we choose to join.
312 * (For example, in a 3-base-rel join, a clause relating rels 1 and 2 must be
313 * treated as a restrictclause if we join {1} and {2 3} to make {1 2 3}; but
314 * if we join {1 2} and {3} then that clause will be a restrictclause in {1 2}
315 * and should not be processed again at the level of {1 2 3}.) Therefore,
316 * the restrictinfo list in the join case appears in individual JoinPaths
317 * (field joinrestrictinfo), not in the parent relation. But it's OK for
318 * the RelOptInfo to store the joininfo list, because that is the same
319 * for a given rel no matter how we form it.
321 * We store baserestrictcost in the RelOptInfo (for base relations) because
322 * we know we will need it at least once (to price the sequential scan)
323 * and may need it multiple times to price index scans.
326 typedef enum RelOptKind
330 RELOPT_OTHER_MEMBER_REL
333 typedef struct RelOptInfo
337 RelOptKind reloptkind;
339 /* all relations included in this RelOptInfo */
340 Relids relids; /* set of base relids (rangetable indexes) */
342 /* size estimates generated by planner */
343 double rows; /* estimated number of result tuples */
344 int width; /* estimated avg width of result tuples */
346 /* materialization information */
347 List *reltargetlist; /* Vars to be output by scan of relation */
348 List *pathlist; /* Path structures */
349 struct Path *cheapest_startup_path;
350 struct Path *cheapest_total_path;
351 struct Path *cheapest_unique_path;
353 /* information about a base rel (not set for join rels!) */
355 RTEKind rtekind; /* RELATION, SUBQUERY, or FUNCTION */
356 AttrNumber min_attr; /* smallest attrno of rel (often <0) */
357 AttrNumber max_attr; /* largest attrno of rel */
358 Relids *attr_needed; /* array indexed [min_attr .. max_attr] */
359 int32 *attr_widths; /* array indexed [min_attr .. max_attr] */
360 List *indexlist; /* list of IndexOptInfo */
363 struct Plan *subplan; /* if subquery */
364 List *subrtable; /* if subquery */
366 /* used by various scans and joins: */
367 List *baserestrictinfo; /* RestrictInfo structures (if base
369 QualCost baserestrictcost; /* cost of evaluating the above */
370 List *joininfo; /* RestrictInfo structures for join clauses
371 * involving this rel */
372 bool has_eclass_joins; /* T means joininfo is incomplete */
374 /* cached info about inner indexscan paths for relation: */
375 Relids index_outer_relids; /* other relids in indexable join
377 List *index_inner_paths; /* InnerIndexscanInfo nodes */
380 * Inner indexscans are not in the main pathlist because they are not
381 * usable except in specific join contexts. We use the index_inner_paths
382 * list just to avoid recomputing the best inner indexscan repeatedly for
383 * similar outer relations. See comments for InnerIndexscanInfo.
389 * Per-index information for planning/optimization
391 * Prior to Postgres 7.0, RelOptInfo was used to describe both relations
392 * and indexes, but that created confusion without actually doing anything
393 * useful. So now we have a separate IndexOptInfo struct for indexes.
395 * opfamily[], indexkeys[], opcintype[], fwdsortop[], revsortop[],
396 * and nulls_first[] each have ncolumns entries.
397 * Note: for historical reasons, the opfamily array has an extra entry
398 * that is always zero. Some code scans until it sees a zero entry,
399 * rather than looking at ncolumns.
401 * Zeroes in the indexkeys[] array indicate index columns that are
402 * expressions; there is one element in indexprs for each such column.
404 * For an unordered index, the sortop arrays contains zeroes. Note that
405 * fwdsortop[] and nulls_first[] describe the sort ordering of a forward
406 * indexscan; we can also consider a backward indexscan, which will
407 * generate sort order described by revsortop/!nulls_first.
409 * The indexprs and indpred expressions have been run through
410 * prepqual.c and eval_const_expressions() for ease of matching to
411 * WHERE clauses. indpred is in implicit-AND form.
413 typedef struct IndexOptInfo
417 Oid indexoid; /* OID of the index relation */
418 RelOptInfo *rel; /* back-link to index's table */
420 /* statistics from pg_class */
421 BlockNumber pages; /* number of disk pages in index */
422 double tuples; /* number of index tuples in index */
424 /* index descriptor information */
425 int ncolumns; /* number of columns in index */
426 Oid *opfamily; /* OIDs of operator families for columns */
427 int *indexkeys; /* column numbers of index's keys, or 0 */
428 Oid *opcintype; /* OIDs of opclass declared input data types */
429 Oid *fwdsortop; /* OIDs of sort operators for each column */
430 Oid *revsortop; /* OIDs of sort operators for backward scan */
431 bool *nulls_first; /* do NULLs come first in the sort order? */
432 Oid relam; /* OID of the access method (in pg_am) */
434 RegProcedure amcostestimate; /* OID of the access method's cost fcn */
436 List *indexprs; /* expressions for non-simple index columns */
437 List *indpred; /* predicate if a partial index, else NIL */
439 bool predOK; /* true if predicate matches query */
440 bool unique; /* true if a unique index */
441 bool amoptionalkey; /* can query omit key for the first column? */
442 bool amsearchnulls; /* can AM search for NULL index entries? */
449 * Whenever we can determine that a mergejoinable equality clause A = B is
450 * not delayed by any outer join, we create an EquivalenceClass containing
451 * the expressions A and B to record this knowledge. If we later find another
452 * equivalence B = C, we add C to the existing EquivalenceClass; this may
453 * require merging two existing EquivalenceClasses. At the end of the qual
454 * distribution process, we have sets of values that are known all transitively
455 * equal to each other, where "equal" is according to the rules of the btree
456 * operator family(s) shown in ec_opfamilies. (We restrict an EC to contain
457 * only equalities whose operators belong to the same set of opfamilies. This
458 * could probably be relaxed, but for now it's not worth the trouble, since
459 * nearly all equality operators belong to only one btree opclass anyway.)
461 * We also use EquivalenceClasses as the base structure for PathKeys, letting
462 * us represent knowledge about different sort orderings being equivalent.
463 * Since every PathKey must reference an EquivalenceClass, we will end up
464 * with single-member EquivalenceClasses whenever a sort key expression has
465 * not been equivalenced to anything else. It is also possible that such an
466 * EquivalenceClass will contain a volatile expression ("ORDER BY random()"),
467 * which is a case that can't arise otherwise since clauses containing
468 * volatile functions are never considered mergejoinable. We mark such
469 * EquivalenceClasses specially to prevent them from being merged with
470 * ordinary EquivalenceClasses. Also, for volatile expressions we have
471 * to be careful to match the EquivalenceClass to the correct targetlist
472 * entry: consider SELECT random() AS a, random() AS b ... ORDER BY b,a.
473 * So we record the SortGroupRef of the originating sort clause.
475 * We allow equality clauses appearing below the nullable side of an outer join
476 * to form EquivalenceClasses, but these have a slightly different meaning:
477 * the included values might be all NULL rather than all the same non-null
478 * values. See src/backend/optimizer/README for more on that point.
480 * NB: if ec_merged isn't NULL, this class has been merged into another, and
481 * should be ignored in favor of using the pointed-to class.
483 typedef struct EquivalenceClass
487 List *ec_opfamilies; /* btree operator family OIDs */
488 List *ec_members; /* list of EquivalenceMembers */
489 List *ec_sources; /* list of generating RestrictInfos */
490 List *ec_derives; /* list of derived RestrictInfos */
491 Relids ec_relids; /* all relids appearing in ec_members */
492 bool ec_has_const; /* any pseudoconstants in ec_members? */
493 bool ec_has_volatile; /* the (sole) member is a volatile expr */
494 bool ec_below_outer_join; /* equivalence applies below an OJ */
495 bool ec_broken; /* failed to generate needed clauses? */
496 Index ec_sortref; /* originating sortclause label, or 0 */
497 struct EquivalenceClass *ec_merged; /* set if merged into another EC */
501 * If an EC contains a const and isn't below-outer-join, any PathKey depending
502 * on it must be redundant, since there's only one possible value of the key.
504 #define EC_MUST_BE_REDUNDANT(eclass) \
505 ((eclass)->ec_has_const && !(eclass)->ec_below_outer_join)
508 * EquivalenceMember - one member expression of an EquivalenceClass
510 * em_is_child signifies that this element was built by transposing a member
511 * for an inheritance parent relation to represent the corresponding expression
512 * on an inheritance child. The element should be ignored for all purposes
513 * except constructing inner-indexscan paths for the child relation. (Other
514 * types of join are driven from transposed joininfo-list entries.) Note
515 * that the EC's ec_relids field does NOT include the child relation.
517 * em_datatype is usually the same as exprType(em_expr), but can be
518 * different when dealing with a binary-compatible opfamily; in particular
519 * anyarray_ops would never work without this. Use em_datatype when
520 * looking up a specific btree operator to work with this expression.
522 typedef struct EquivalenceMember
526 Expr *em_expr; /* the expression represented */
527 Relids em_relids; /* all relids appearing in em_expr */
528 bool em_is_const; /* expression is pseudoconstant? */
529 bool em_is_child; /* derived version for a child relation? */
530 Oid em_datatype; /* the "nominal type" used by the opfamily */
536 * The sort ordering of a path is represented by a list of PathKey nodes.
537 * An empty list implies no known ordering. Otherwise the first item
538 * represents the primary sort key, the second the first secondary sort key,
539 * etc. The value being sorted is represented by linking to an
540 * EquivalenceClass containing that value and including pk_opfamily among its
541 * ec_opfamilies. This is a convenient method because it makes it trivial
542 * to detect equivalent and closely-related orderings. (See optimizer/README
543 * for more information.)
545 * Note: pk_strategy is either BTLessStrategyNumber (for ASC) or
546 * BTGreaterStrategyNumber (for DESC). We assume that all ordering-capable
547 * index types will use btree-compatible strategy numbers.
550 typedef struct PathKey
554 EquivalenceClass *pk_eclass; /* the value that is ordered */
555 Oid pk_opfamily; /* btree opfamily defining the ordering */
556 int pk_strategy; /* sort direction (ASC or DESC) */
557 bool pk_nulls_first; /* do NULLs come before normal values? */
561 * Type "Path" is used as-is for sequential-scan paths, as well as some other
562 * simple plan types that we don't need any extra information in the path for.
563 * For other path types it is the first component of a larger struct.
565 * Note: "pathtype" is the NodeTag of the Plan node we could build from this
566 * Path. It is partially redundant with the Path's NodeTag, but allows us
567 * to use the same Path type for multiple Plan types where there is no need
568 * to distinguish the Plan type during path processing.
575 NodeTag pathtype; /* tag identifying scan/join method */
577 RelOptInfo *parent; /* the relation this path can build */
579 /* estimated execution costs for path (see costsize.c for more info) */
580 Cost startup_cost; /* cost expended before fetching any tuples */
581 Cost total_cost; /* total cost (assuming all tuples fetched) */
583 List *pathkeys; /* sort ordering of path's output */
584 /* pathkeys is a List of PathKey nodes; see above */
588 * IndexPath represents an index scan over a single index.
590 * 'indexinfo' is the index to be scanned.
592 * 'indexclauses' is a list of index qualification clauses, with implicit
593 * AND semantics across the list. Each clause is a RestrictInfo node from
594 * the query's WHERE or JOIN conditions.
596 * 'indexquals' has the same structure as 'indexclauses', but it contains
597 * the actual indexqual conditions that can be used with the index.
598 * In simple cases this is identical to 'indexclauses', but when special
599 * indexable operators appear in 'indexclauses', they are replaced by the
600 * derived indexscannable conditions in 'indexquals'.
602 * 'isjoininner' is TRUE if the path is a nestloop inner scan (that is,
603 * some of the index conditions are join rather than restriction clauses).
604 * Note that the path costs will be calculated differently from a plain
605 * indexscan in this case, and in addition there's a special 'rows' value
606 * different from the parent RelOptInfo's (see below).
608 * 'indexscandir' is one of:
609 * ForwardScanDirection: forward scan of an ordered index
610 * BackwardScanDirection: backward scan of an ordered index
611 * NoMovementScanDirection: scan of an unordered index, or don't care
612 * (The executor doesn't care whether it gets ForwardScanDirection or
613 * NoMovementScanDirection for an indexscan, but the planner wants to
614 * distinguish ordered from unordered indexes for building pathkeys.)
616 * 'indextotalcost' and 'indexselectivity' are saved in the IndexPath so that
617 * we need not recompute them when considering using the same index in a
618 * bitmap index/heap scan (see BitmapHeapPath). The costs of the IndexPath
619 * itself represent the costs of an IndexScan plan type.
621 * 'rows' is the estimated result tuple count for the indexscan. This
622 * is the same as path.parent->rows for a simple indexscan, but it is
623 * different for a nestloop inner scan, because the additional indexquals
624 * coming from join clauses make the scan more selective than the parent
625 * rel's restrict clauses alone would do.
628 typedef struct IndexPath
631 IndexOptInfo *indexinfo;
635 ScanDirection indexscandir;
637 Selectivity indexselectivity;
638 double rows; /* estimated number of result tuples */
642 * BitmapHeapPath represents one or more indexscans that generate TID bitmaps
643 * instead of directly accessing the heap, followed by AND/OR combinations
644 * to produce a single bitmap, followed by a heap scan that uses the bitmap.
645 * Note that the output is always considered unordered, since it will come
646 * out in physical heap order no matter what the underlying indexes did.
648 * The individual indexscans are represented by IndexPath nodes, and any
649 * logic on top of them is represented by a tree of BitmapAndPath and
650 * BitmapOrPath nodes. Notice that we can use the same IndexPath node both
651 * to represent a regular IndexScan plan, and as the child of a BitmapHeapPath
652 * that represents scanning the same index using a BitmapIndexScan. The
653 * startup_cost and total_cost figures of an IndexPath always represent the
654 * costs to use it as a regular IndexScan. The costs of a BitmapIndexScan
655 * can be computed using the IndexPath's indextotalcost and indexselectivity.
657 * BitmapHeapPaths can be nestloop inner indexscans. The isjoininner and
658 * rows fields serve the same purpose as for plain IndexPaths.
660 typedef struct BitmapHeapPath
663 Path *bitmapqual; /* IndexPath, BitmapAndPath, BitmapOrPath */
664 bool isjoininner; /* T if it's a nestloop inner scan */
665 double rows; /* estimated number of result tuples */
669 * BitmapAndPath represents a BitmapAnd plan node; it can only appear as
670 * part of the substructure of a BitmapHeapPath. The Path structure is
671 * a bit more heavyweight than we really need for this, but for simplicity
672 * we make it a derivative of Path anyway.
674 typedef struct BitmapAndPath
677 List *bitmapquals; /* IndexPaths and BitmapOrPaths */
678 Selectivity bitmapselectivity;
682 * BitmapOrPath represents a BitmapOr plan node; it can only appear as
683 * part of the substructure of a BitmapHeapPath. The Path structure is
684 * a bit more heavyweight than we really need for this, but for simplicity
685 * we make it a derivative of Path anyway.
687 typedef struct BitmapOrPath
690 List *bitmapquals; /* IndexPaths and BitmapAndPaths */
691 Selectivity bitmapselectivity;
695 * TidPath represents a scan by TID
697 * tidquals is an implicitly OR'ed list of qual expressions of the form
698 * "CTID = pseudoconstant" or "CTID = ANY(pseudoconstant_array)".
699 * Note they are bare expressions, not RestrictInfos.
701 typedef struct TidPath
704 List *tidquals; /* qual(s) involving CTID = something */
708 * AppendPath represents an Append plan, ie, successive execution of
709 * several member plans.
711 * Note: it is possible for "subpaths" to contain only one, or even no,
712 * elements. These cases are optimized during create_append_plan.
713 * In particular, an AppendPath with no subpaths is a "dummy" path that
714 * is created to represent the case that a relation is provably empty.
716 typedef struct AppendPath
719 List *subpaths; /* list of component Paths */
722 #define IS_DUMMY_PATH(p) \
723 (IsA((p), AppendPath) && ((AppendPath *) (p))->subpaths == NIL)
726 * ResultPath represents use of a Result plan node to compute a variable-free
727 * targetlist with no underlying tables (a "SELECT expressions" query).
728 * The query could have a WHERE clause, too, represented by "quals".
730 * Note that quals is a list of bare clauses, not RestrictInfos.
732 typedef struct ResultPath
739 * MaterialPath represents use of a Material plan node, i.e., caching of
740 * the output of its subpath. This is used when the subpath is expensive
741 * and needs to be scanned repeatedly, or when we need mark/restore ability
742 * and the subpath doesn't have it.
744 typedef struct MaterialPath
751 * UniquePath represents elimination of distinct rows from the output of
754 * This is unlike the other Path nodes in that it can actually generate
755 * different plans: either hash-based or sort-based implementation, or a
756 * no-op if the input path can be proven distinct already. The decision
757 * is sufficiently localized that it's not worth having separate Path node
758 * types. (Note: in the no-op case, we could eliminate the UniquePath node
759 * entirely and just return the subpath; but it's convenient to have a
760 * UniquePath in the path tree to signal upper-level routines that the input
761 * is known distinct.)
765 UNIQUE_PATH_NOOP, /* input is known unique already */
766 UNIQUE_PATH_HASH, /* use hashing */
767 UNIQUE_PATH_SORT /* use sorting */
770 typedef struct UniquePath
774 UniquePathMethod umethod;
775 List *in_operators; /* equality operators of the IN clause */
776 List *uniq_exprs; /* expressions to be made unique */
777 double rows; /* estimated number of result tuples */
781 * All join-type paths share these fields.
784 typedef struct JoinPath
790 Path *outerjoinpath; /* path for the outer side of the join */
791 Path *innerjoinpath; /* path for the inner side of the join */
793 List *joinrestrictinfo; /* RestrictInfos to apply to join */
796 * See the notes for RelOptInfo to understand why joinrestrictinfo is
797 * needed in JoinPath, and can't be merged into the parent RelOptInfo.
802 * A nested-loop path needs no special fields.
805 typedef JoinPath NestPath;
808 * A mergejoin path has these fields.
810 * path_mergeclauses lists the clauses (in the form of RestrictInfos)
811 * that will be used in the merge.
813 * Note that the mergeclauses are a subset of the parent relation's
814 * restriction-clause list. Any join clauses that are not mergejoinable
815 * appear only in the parent's restrict list, and must be checked by a
816 * qpqual at execution time.
818 * outersortkeys (resp. innersortkeys) is NIL if the outer path
819 * (resp. inner path) is already ordered appropriately for the
820 * mergejoin. If it is not NIL then it is a PathKeys list describing
821 * the ordering that must be created by an explicit sort step.
824 typedef struct MergePath
827 List *path_mergeclauses; /* join clauses to be used for merge */
828 List *outersortkeys; /* keys for explicit sort, if any */
829 List *innersortkeys; /* keys for explicit sort, if any */
833 * A hashjoin path has these fields.
835 * The remarks above for mergeclauses apply for hashclauses as well.
837 * Hashjoin does not care what order its inputs appear in, so we have
838 * no need for sortkeys.
841 typedef struct HashPath
844 List *path_hashclauses; /* join clauses used for hashing */
848 * Restriction clause info.
850 * We create one of these for each AND sub-clause of a restriction condition
851 * (WHERE or JOIN/ON clause). Since the restriction clauses are logically
852 * ANDed, we can use any one of them or any subset of them to filter out
853 * tuples, without having to evaluate the rest. The RestrictInfo node itself
854 * stores data used by the optimizer while choosing the best query plan.
856 * If a restriction clause references a single base relation, it will appear
857 * in the baserestrictinfo list of the RelOptInfo for that base rel.
859 * If a restriction clause references more than one base rel, it will
860 * appear in the joininfo list of every RelOptInfo that describes a strict
861 * subset of the base rels mentioned in the clause. The joininfo lists are
862 * used to drive join tree building by selecting plausible join candidates.
863 * The clause cannot actually be applied until we have built a join rel
864 * containing all the base rels it references, however.
866 * When we construct a join rel that includes all the base rels referenced
867 * in a multi-relation restriction clause, we place that clause into the
868 * joinrestrictinfo lists of paths for the join rel, if neither left nor
869 * right sub-path includes all base rels referenced in the clause. The clause
870 * will be applied at that join level, and will not propagate any further up
871 * the join tree. (Note: the "predicate migration" code was once intended to
872 * push restriction clauses up and down the plan tree based on evaluation
873 * costs, but it's dead code and is unlikely to be resurrected in the
874 * foreseeable future.)
876 * Note that in the presence of more than two rels, a multi-rel restriction
877 * might reach different heights in the join tree depending on the join
878 * sequence we use. So, these clauses cannot be associated directly with
879 * the join RelOptInfo, but must be kept track of on a per-join-path basis.
881 * RestrictInfos that represent equivalence conditions (i.e., mergejoinable
882 * equalities that are not outerjoin-delayed) are handled a bit differently.
883 * Initially we attach them to the EquivalenceClasses that are derived from
884 * them. When we construct a scan or join path, we look through all the
885 * EquivalenceClasses and generate derived RestrictInfos representing the
886 * minimal set of conditions that need to be checked for this particular scan
887 * or join to enforce that all members of each EquivalenceClass are in fact
888 * equal in all rows emitted by the scan or join.
890 * When dealing with outer joins we have to be very careful about pushing qual
891 * clauses up and down the tree. An outer join's own JOIN/ON conditions must
892 * be evaluated exactly at that join node, unless they are "degenerate"
893 * conditions that reference only Vars from the nullable side of the join.
894 * Quals appearing in WHERE or in a JOIN above the outer join cannot be pushed
895 * down below the outer join, if they reference any nullable Vars.
896 * RestrictInfo nodes contain a flag to indicate whether a qual has been
897 * pushed down to a lower level than its original syntactic placement in the
898 * join tree would suggest. If an outer join prevents us from pushing a qual
899 * down to its "natural" semantic level (the level associated with just the
900 * base rels used in the qual) then we mark the qual with a "required_relids"
901 * value including more than just the base rels it actually uses. By
902 * pretending that the qual references all the rels required to form the outer
903 * join, we prevent it from being evaluated below the outer join's joinrel.
904 * When we do form the outer join's joinrel, we still need to distinguish
905 * those quals that are actually in that join's JOIN/ON condition from those
906 * that appeared elsewhere in the tree and were pushed down to the join rel
907 * because they used no other rels. That's what the is_pushed_down flag is
908 * for; it tells us that a qual is not an OUTER JOIN qual for the set of base
909 * rels listed in required_relids. A clause that originally came from WHERE
910 * or an INNER JOIN condition will *always* have its is_pushed_down flag set.
911 * It's possible for an OUTER JOIN clause to be marked is_pushed_down too,
912 * if we decide that it can be pushed down into the nullable side of the join.
913 * In that case it acts as a plain filter qual for wherever it gets evaluated.
914 * (In short, is_pushed_down is only false for non-degenerate outer join
915 * conditions. Possibly we should rename it to reflect that meaning?)
917 * RestrictInfo nodes also contain an outerjoin_delayed flag, which is true
918 * if the clause's applicability must be delayed due to any outer joins
919 * appearing below its own syntactic level (ie, it references any Vars from
920 * the nullable side of any lower outer join).
922 * In general, the referenced clause might be arbitrarily complex. The
923 * kinds of clauses we can handle as indexscan quals, mergejoin clauses,
924 * or hashjoin clauses are limited (e.g., no volatile functions). The code
925 * for each kind of path is responsible for identifying the restrict clauses
926 * it can use and ignoring the rest. Clauses not implemented by an indexscan,
927 * mergejoin, or hashjoin will be placed in the plan qual or joinqual field
928 * of the finished Plan node, where they will be enforced by general-purpose
929 * qual-expression-evaluation code. (But we are still entitled to count
930 * their selectivity when estimating the result tuple count, if we
931 * can guess what it is...)
933 * When the referenced clause is an OR clause, we generate a modified copy
934 * in which additional RestrictInfo nodes are inserted below the top-level
935 * OR/AND structure. This is a convenience for OR indexscan processing:
936 * indexquals taken from either the top level or an OR subclause will have
937 * associated RestrictInfo nodes.
939 * The can_join flag is set true if the clause looks potentially useful as
940 * a merge or hash join clause, that is if it is a binary opclause with
941 * nonoverlapping sets of relids referenced in the left and right sides.
942 * (Whether the operator is actually merge or hash joinable isn't checked,
945 * The pseudoconstant flag is set true if the clause contains no Vars of
946 * the current query level and no volatile functions. Such a clause can be
947 * pulled out and used as a one-time qual in a gating Result node. We keep
948 * pseudoconstant clauses in the same lists as other RestrictInfos so that
949 * the regular clause-pushing machinery can assign them to the correct join
950 * level, but they need to be treated specially for cost and selectivity
951 * estimates. Note that a pseudoconstant clause can never be an indexqual
952 * or merge or hash join clause, so it's of no interest to large parts of
955 * When join clauses are generated from EquivalenceClasses, there may be
956 * several equally valid ways to enforce join equivalence, of which we need
957 * apply only one. We mark clauses of this kind by setting parent_ec to
958 * point to the generating EquivalenceClass. Multiple clauses with the same
959 * parent_ec in the same join are redundant.
962 typedef struct RestrictInfo
966 Expr *clause; /* the represented clause of WHERE or JOIN */
968 bool is_pushed_down; /* TRUE if clause was pushed down in level */
970 bool outerjoin_delayed; /* TRUE if delayed by lower outer join */
972 bool can_join; /* see comment above */
974 bool pseudoconstant; /* see comment above */
976 /* The set of relids (varnos) actually referenced in the clause: */
977 Relids clause_relids;
979 /* The set of relids required to evaluate the clause: */
980 Relids required_relids;
982 /* These fields are set for any binary opclause: */
983 Relids left_relids; /* relids in left side of clause */
984 Relids right_relids; /* relids in right side of clause */
986 /* This field is NULL unless clause is an OR clause: */
987 Expr *orclause; /* modified clause with RestrictInfos */
989 /* This field is NULL unless clause is potentially redundant: */
990 EquivalenceClass *parent_ec; /* generating EquivalenceClass */
992 /* cache space for cost and selectivity */
993 QualCost eval_cost; /* eval cost of clause; -1 if not yet set */
994 Selectivity this_selec; /* selectivity; -1 if not yet set */
996 /* valid if clause is mergejoinable, else NIL */
997 List *mergeopfamilies; /* opfamilies containing clause operator */
999 /* cache space for mergeclause processing; NULL if not yet set */
1000 EquivalenceClass *left_ec; /* EquivalenceClass containing lefthand */
1001 EquivalenceClass *right_ec; /* EquivalenceClass containing righthand */
1002 EquivalenceMember *left_em; /* EquivalenceMember for lefthand */
1003 EquivalenceMember *right_em; /* EquivalenceMember for righthand */
1004 List *scansel_cache; /* list of MergeScanSelCache structs */
1006 /* transient workspace for use while considering a specific join path */
1007 bool outer_is_left; /* T = outer var on left, F = on right */
1009 /* valid if clause is hashjoinable, else InvalidOid: */
1010 Oid hashjoinoperator; /* copy of clause operator */
1012 /* cache space for hashclause processing; -1 if not yet set */
1013 Selectivity left_bucketsize; /* avg bucketsize of left side */
1014 Selectivity right_bucketsize; /* avg bucketsize of right side */
1018 * Since mergejoinscansel() is a relatively expensive function, and would
1019 * otherwise be invoked many times while planning a large join tree,
1020 * we go out of our way to cache its results. Each mergejoinable
1021 * RestrictInfo carries a list of the specific sort orderings that have
1022 * been considered for use with it, and the resulting selectivities.
1024 typedef struct MergeScanSelCache
1026 /* Ordering details (cache lookup key) */
1027 Oid opfamily; /* btree opfamily defining the ordering */
1028 int strategy; /* sort direction (ASC or DESC) */
1029 bool nulls_first; /* do NULLs come before normal values? */
1031 Selectivity leftstartsel; /* first-join fraction for clause left side */
1032 Selectivity leftendsel; /* last-join fraction for clause left side */
1033 Selectivity rightstartsel; /* first-join fraction for clause right side */
1034 Selectivity rightendsel; /* last-join fraction for clause right side */
1035 } MergeScanSelCache;
1038 * Inner indexscan info.
1040 * An inner indexscan is one that uses one or more joinclauses as index
1041 * conditions (perhaps in addition to plain restriction clauses). So it
1042 * can only be used as the inner path of a nestloop join where the outer
1043 * relation includes all other relids appearing in those joinclauses.
1044 * The set of usable joinclauses, and thus the best inner indexscan,
1045 * thus varies depending on which outer relation we consider; so we have
1046 * to recompute the best such paths for every join. To avoid lots of
1047 * redundant computation, we cache the results of such searches. For
1048 * each relation we compute the set of possible otherrelids (all relids
1049 * appearing in joinquals that could become indexquals for this table).
1050 * Two outer relations whose relids have the same intersection with this
1051 * set will have the same set of available joinclauses and thus the same
1052 * best inner indexscans for the inner relation. By taking the intersection
1053 * before scanning the cache, we avoid recomputing when considering
1054 * join rels that differ only by the inclusion of irrelevant other rels.
1056 * The search key also includes a bool showing whether the join being
1057 * considered is an outer join. Since we constrain the join order for
1058 * outer joins, I believe that this bool can only have one possible value
1059 * for any particular lookup key; but store it anyway to avoid confusion.
1062 typedef struct InnerIndexscanInfo
1065 /* The lookup key: */
1066 Relids other_relids; /* a set of relevant other relids */
1067 bool isouterjoin; /* true if join is outer */
1068 /* Best paths for this lookup key (NULL if no available indexscans): */
1069 Path *cheapest_startup_innerpath; /* cheapest startup cost */
1070 Path *cheapest_total_innerpath; /* cheapest total cost */
1071 } InnerIndexscanInfo;
1074 * "Flattened SubLinks"
1076 * When we pull an IN or EXISTS SubLink up into the parent query, the
1077 * join conditions extracted from the IN/EXISTS clause need to be specially
1078 * treated in distribute_qual_to_rels processing. We handle this by
1079 * wrapping such expressions in a FlattenedSubLink node that identifies
1080 * the join they come from. The FlattenedSubLink node is discarded after
1081 * distribute_qual_to_rels, having served its purpose.
1083 * Although the planner treats this as an expression node type, it is not
1084 * recognized by the parser or executor, so we declare it here rather than
1088 typedef struct FlattenedSubLink
1091 JoinType jointype; /* must be JOIN_SEMI or JOIN_ANTI */
1092 Relids lefthand; /* base relids treated as syntactic LHS */
1093 Relids righthand; /* base relids syntactically within RHS */
1094 Expr *quals; /* join quals (in explicit-AND format) */
1098 * Placeholder node for an expression to be evaluated below the top level
1099 * of a plan tree. This is used during planning to represent the contained
1100 * expression. At the end of the planning process it is replaced by either
1101 * the contained expression or a Var referring to a lower-level evaluation of
1102 * the contained expression. Typically the evaluation occurs below an outer
1103 * join, and Var references above the outer join might thereby yield NULL
1104 * instead of the expression value.
1106 * Although the planner treats this as an expression node type, it is not
1107 * recognized by the parser or executor, so we declare it here rather than
1111 typedef struct PlaceHolderVar
1114 Expr *phexpr; /* the represented expression */
1115 Relids phrels; /* base relids syntactically within expr src */
1116 Index phid; /* ID for PHV (unique within planner run) */
1117 Index phlevelsup; /* > 0 if PHV belongs to outer query */
1121 * "Special join" info.
1123 * One-sided outer joins constrain the order of joining partially but not
1124 * completely. We flatten such joins into the planner's top-level list of
1125 * relations to join, but record information about each outer join in a
1126 * SpecialJoinInfo struct. These structs are kept in the PlannerInfo node's
1129 * Similarly, semijoins and antijoins created by flattening IN (subselect)
1130 * and EXISTS(subselect) clauses create partial constraints on join order.
1131 * These are likewise recorded in SpecialJoinInfo structs.
1133 * We make SpecialJoinInfos for FULL JOINs even though there is no flexibility
1134 * of planning for them, because this simplifies make_join_rel()'s API.
1136 * min_lefthand and min_righthand are the sets of base relids that must be
1137 * available on each side when performing the special join. lhs_strict is
1138 * true if the special join's condition cannot succeed when the LHS variables
1139 * are all NULL (this means that an outer join can commute with upper-level
1140 * outer joins even if it appears in their RHS). We don't bother to set
1141 * lhs_strict for FULL JOINs, however.
1143 * It is not valid for either min_lefthand or min_righthand to be empty sets;
1144 * if they were, this would break the logic that enforces join order.
1146 * syn_lefthand and syn_righthand are the sets of base relids that are
1147 * syntactically below this special join. (These are needed to help compute
1148 * min_lefthand and min_righthand for higher joins.)
1150 * delay_upper_joins is set TRUE if we detect a pushed-down clause that has
1151 * to be evaluated after this join is formed (because it references the RHS).
1152 * Any outer joins that have such a clause and this join in their RHS cannot
1153 * commute with this join, because that would leave noplace to check the
1154 * pushed-down clause. (We don't track this for FULL JOINs, either.)
1156 * join_quals is an implicit-AND list of the quals syntactically associated
1157 * with the join (they may or may not end up being applied at the join level).
1158 * This is just a side list and does not drive actual application of quals.
1159 * For JOIN_SEMI joins, this is cleared to NIL in create_unique_path() if
1160 * the join is found not to be suitable for a uniqueify-the-RHS plan.
1162 * jointype is never JOIN_RIGHT; a RIGHT JOIN is handled by switching
1163 * the inputs to make it a LEFT JOIN. So the allowed values of jointype
1164 * in a join_info_list member are only LEFT, FULL, SEMI, or ANTI.
1166 * For purposes of join selectivity estimation, we create transient
1167 * SpecialJoinInfo structures for regular inner joins; so it is possible
1168 * to have jointype == JOIN_INNER in such a structure, even though this is
1169 * not allowed within join_info_list. Note that lhs_strict, delay_upper_joins,
1170 * and join_quals are not set meaningfully for such structs.
1173 typedef struct SpecialJoinInfo
1176 Relids min_lefthand; /* base relids in minimum LHS for join */
1177 Relids min_righthand; /* base relids in minimum RHS for join */
1178 Relids syn_lefthand; /* base relids syntactically within LHS */
1179 Relids syn_righthand; /* base relids syntactically within RHS */
1180 JoinType jointype; /* always INNER, LEFT, FULL, SEMI, or ANTI */
1181 bool lhs_strict; /* joinclause is strict for some LHS rel */
1182 bool delay_upper_joins; /* can't commute with upper RHS */
1183 List *join_quals; /* join quals, in implicit-AND list format */
1187 * Append-relation info.
1189 * When we expand an inheritable table or a UNION-ALL subselect into an
1190 * "append relation" (essentially, a list of child RTEs), we build an
1191 * AppendRelInfo for each child RTE. The list of AppendRelInfos indicates
1192 * which child RTEs must be included when expanding the parent, and each
1193 * node carries information needed to translate Vars referencing the parent
1194 * into Vars referencing that child.
1196 * These structs are kept in the PlannerInfo node's append_rel_list.
1197 * Note that we just throw all the structs into one list, and scan the
1198 * whole list when desiring to expand any one parent. We could have used
1199 * a more complex data structure (eg, one list per parent), but this would
1200 * be harder to update during operations such as pulling up subqueries,
1201 * and not really any easier to scan. Considering that typical queries
1202 * will not have many different append parents, it doesn't seem worthwhile
1203 * to complicate things.
1205 * Note: after completion of the planner prep phase, any given RTE is an
1206 * append parent having entries in append_rel_list if and only if its
1207 * "inh" flag is set. We clear "inh" for plain tables that turn out not
1208 * to have inheritance children, and (in an abuse of the original meaning
1209 * of the flag) we set "inh" for subquery RTEs that turn out to be
1210 * flattenable UNION ALL queries. This lets us avoid useless searches
1211 * of append_rel_list.
1213 * Note: the data structure assumes that append-rel members are single
1214 * baserels. This is OK for inheritance, but it prevents us from pulling
1215 * up a UNION ALL member subquery if it contains a join. While that could
1216 * be fixed with a more complex data structure, at present there's not much
1217 * point because no improvement in the plan could result.
1220 typedef struct AppendRelInfo
1225 * These fields uniquely identify this append relationship. There can be
1226 * (in fact, always should be) multiple AppendRelInfos for the same
1227 * parent_relid, but never more than one per child_relid, since a given
1228 * RTE cannot be a child of more than one append parent.
1230 Index parent_relid; /* RT index of append parent rel */
1231 Index child_relid; /* RT index of append child rel */
1234 * For an inheritance appendrel, the parent and child are both regular
1235 * relations, and we store their rowtype OIDs here for use in translating
1236 * whole-row Vars. For a UNION-ALL appendrel, the parent and child are
1237 * both subqueries with no named rowtype, and we store InvalidOid here.
1239 Oid parent_reltype; /* OID of parent's composite type */
1240 Oid child_reltype; /* OID of child's composite type */
1243 * The N'th element of this list is the integer column number of the child
1244 * column corresponding to the N'th column of the parent. A list element
1245 * is zero if it corresponds to a dropped column of the parent (this is
1246 * only possible for inheritance cases, not UNION ALL).
1248 List *col_mappings; /* list of child attribute numbers */
1251 * The N'th element of this list is a Var or expression representing the
1252 * child column corresponding to the N'th column of the parent. This is
1253 * used to translate Vars referencing the parent rel into references to
1254 * the child. A list element is NULL if it corresponds to a dropped
1255 * column of the parent (this is only possible for inheritance cases, not
1258 * This might seem redundant with the col_mappings data, but it is handy
1259 * because flattening of sub-SELECTs that are members of a UNION ALL will
1260 * cause changes in the expressions that need to be substituted for a
1261 * parent Var. Adjusting this data structure lets us track what really
1262 * needs to be substituted.
1264 * Notice we only store entries for user columns (attno > 0). Whole-row
1265 * Vars are special-cased, and system columns (attno < 0) need no special
1266 * translation since their attnos are the same for all tables.
1268 * Caution: the Vars have varlevelsup = 0. Be careful to adjust as needed
1269 * when copying into a subquery.
1271 List *translated_vars; /* Expressions in the child's Vars */
1274 * We store the parent table's OID here for inheritance, or InvalidOid for
1275 * UNION ALL. This is only needed to help in generating error messages if
1276 * an attempt is made to reference a dropped parent column.
1278 Oid parent_reloid; /* OID of parent relation */
1282 * For each distinct placeholder expression generated during planning, we
1283 * store a PlaceHolderInfo node in the PlannerInfo node's placeholder_list.
1284 * This stores info that is needed centrally rather than in each copy of the
1285 * PlaceHolderVar. The phid fields identify which PlaceHolderInfo goes with
1286 * each PlaceHolderVar. Note that phid is unique throughout a planner run,
1287 * not just within a query level --- this is so that we need not reassign ID's
1288 * when pulling a subquery into its parent.
1290 * The idea is to evaluate the expression at (only) the ph_eval_at join level,
1291 * then allow it to bubble up like a Var until the ph_needed join level.
1292 * ph_needed has the same definition as attr_needed for a regular Var.
1295 typedef struct PlaceHolderInfo
1299 Index phid; /* ID for PH (unique within planner run) */
1300 PlaceHolderVar *ph_var; /* copy of PlaceHolderVar tree */
1301 Relids ph_eval_at; /* lowest level we can evaluate value at */
1302 Relids ph_needed; /* highest level the value is needed at */
1303 int32 ph_width; /* estimated attribute width */
1307 * glob->paramlist keeps track of the PARAM_EXEC slots that we have decided
1308 * we need for the query. At runtime these slots are used to pass values
1309 * either down into subqueries (for outer references in subqueries) or up out
1310 * of subqueries (for the results of a subplan). The n'th entry in the list
1311 * (n counts from 0) corresponds to Param->paramid = n.
1313 * Each paramlist item shows the absolute query level it is associated with,
1314 * where the outermost query is level 1 and nested subqueries have higher
1315 * numbers. The item the parameter slot represents can be one of three kinds:
1317 * A Var: the slot represents a variable of that level that must be passed
1318 * down because subqueries have outer references to it. The varlevelsup
1319 * value in the Var will always be zero.
1321 * An Aggref (with an expression tree representing its argument): the slot
1322 * represents an aggregate expression that is an outer reference for some
1323 * subquery. The Aggref itself has agglevelsup = 0, and its argument tree
1324 * is adjusted to match in level.
1326 * A Param: the slot holds the result of a subplan (it is a setParam item
1327 * for that subplan). The absolute level shown for such items corresponds
1328 * to the parent query of the subplan.
1330 * Note: we detect duplicate Var parameters and coalesce them into one slot,
1331 * but we do not do this for Aggref or Param slots.
1333 typedef struct PlannerParamItem
1337 Node *item; /* the Var, Aggref, or Param */
1338 Index abslevel; /* its absolute query level */
1341 #endif /* RELATION_H */