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.159 2008/09/09 18:58:08 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 bool transientPlan; /* redo plan when TransactionXmin changes? */
82 /* macro for fetching the Plan associated with a SubPlan node */
83 #define planner_subplan_get_plan(root, subplan) \
84 ((Plan *) list_nth((root)->glob->subplans, (subplan)->plan_id - 1))
89 * Per-query information for planning/optimization
91 * This struct is conventionally called "root" in all the planner routines.
92 * It holds links to all of the planner's working state, in addition to the
93 * original Query. Note that at present the planner extensively modifies
94 * the passed-in Query data structure; someday that should stop.
97 typedef struct PlannerInfo
101 Query *parse; /* the Query being planned */
103 PlannerGlobal *glob; /* global info for current planner run */
105 Index query_level; /* 1 at the outermost Query */
108 * simple_rel_array holds pointers to "base rels" and "other rels" (see
109 * comments for RelOptInfo for more info). It is indexed by rangetable
110 * index (so entry 0 is always wasted). Entries can be NULL when an RTE
111 * does not correspond to a base relation, such as a join RTE or an
112 * unreferenced view RTE; or if the RelOptInfo hasn't been made yet.
114 struct RelOptInfo **simple_rel_array; /* All 1-rel RelOptInfos */
115 int simple_rel_array_size; /* allocated size of array */
118 * simple_rte_array is the same length as simple_rel_array and holds
119 * pointers to the associated rangetable entries. This lets us avoid
120 * rt_fetch(), which can be a bit slow once large inheritance sets have
123 RangeTblEntry **simple_rte_array; /* rangetable as an array */
126 * join_rel_list is a list of all join-relation RelOptInfos we have
127 * considered in this planning run. For small problems we just scan the
128 * list to do lookups, but when there are many join relations we build a
129 * hash table for faster lookups. The hash table is present and valid
130 * when join_rel_hash is not NULL. Note that we still maintain the list
131 * even when using the hash table for lookups; this simplifies life for
134 List *join_rel_list; /* list of join-relation RelOptInfos */
135 struct HTAB *join_rel_hash; /* optional hashtable for join relations */
137 List *resultRelations; /* integer list of RT indexes, or NIL */
139 List *returningLists; /* list of lists of TargetEntry, or NIL */
141 List *init_plans; /* init subplans for query */
143 List *eq_classes; /* list of active EquivalenceClasses */
145 List *canon_pathkeys; /* list of "canonical" PathKeys */
147 List *left_join_clauses; /* list of RestrictInfos for
148 * mergejoinable outer join clauses
149 * w/nonnullable var on left */
151 List *right_join_clauses; /* list of RestrictInfos for
152 * mergejoinable outer join clauses
153 * w/nonnullable var on right */
155 List *full_join_clauses; /* list of RestrictInfos for
156 * mergejoinable full join clauses */
158 List *join_info_list; /* list of SpecialJoinInfos */
160 List *append_rel_list; /* list of AppendRelInfos */
162 List *query_pathkeys; /* desired pathkeys for query_planner(), and
163 * actual pathkeys afterwards */
165 List *group_pathkeys; /* groupClause pathkeys, if any */
166 List *distinct_pathkeys; /* distinctClause pathkeys, if any */
167 List *sort_pathkeys; /* sortClause pathkeys, if any */
169 List *initial_rels; /* RelOptInfos we are now trying to join */
171 MemoryContext planner_cxt; /* context holding PlannerInfo */
173 double total_table_pages; /* # of pages in all tables of query */
175 double tuple_fraction; /* tuple_fraction passed to query_planner */
177 bool hasJoinRTEs; /* true if any RTEs are RTE_JOIN kind */
178 bool hasHavingQual; /* true if havingQual was non-null */
179 bool hasPseudoConstantQuals; /* true if any RestrictInfo has
180 * pseudoconstant = true */
185 * In places where it's known that simple_rte_array[] must have been prepared
186 * already, we just index into it to fetch RTEs. In code that might be
187 * executed before or after entering query_planner(), use this macro.
189 #define planner_rt_fetch(rti, root) \
190 ((root)->simple_rte_array ? (root)->simple_rte_array[rti] : \
191 rt_fetch(rti, (root)->parse->rtable))
196 * Per-relation information for planning/optimization
198 * For planning purposes, a "base rel" is either a plain relation (a table)
199 * or the output of a sub-SELECT or function that appears in the range table.
200 * In either case it is uniquely identified by an RT index. A "joinrel"
201 * is the joining of two or more base rels. A joinrel is identified by
202 * the set of RT indexes for its component baserels. We create RelOptInfo
203 * nodes for each baserel and joinrel, and store them in the PlannerInfo's
204 * simple_rel_array and join_rel_list respectively.
206 * Note that there is only one joinrel for any given set of component
207 * baserels, no matter what order we assemble them in; so an unordered
208 * set is the right datatype to identify it with.
210 * We also have "other rels", which are like base rels in that they refer to
211 * single RT indexes; but they are not part of the join tree, and are given
212 * a different RelOptKind to identify them.
214 * Currently the only kind of otherrels are those made for member relations
215 * of an "append relation", that is an inheritance set or UNION ALL subquery.
216 * An append relation has a parent RTE that is a base rel, which represents
217 * the entire append relation. The member RTEs are otherrels. The parent
218 * is present in the query join tree but the members are not. The member
219 * RTEs and otherrels are used to plan the scans of the individual tables or
220 * subqueries of the append set; then the parent baserel is given an Append
221 * plan comprising the best plans for the individual member rels. (See
222 * comments for AppendRelInfo for more information.)
224 * At one time we also made otherrels to represent join RTEs, for use in
225 * handling join alias Vars. Currently this is not needed because all join
226 * alias Vars are expanded to non-aliased form during preprocess_expression.
228 * Parts of this data structure are specific to various scan and join
229 * mechanisms. It didn't seem worth creating new node types for them.
231 * relids - Set of base-relation identifiers; it is a base relation
232 * if there is just one, a join relation if more than one
233 * rows - estimated number of tuples in the relation after restriction
234 * clauses have been applied (ie, output rows of a plan for it)
235 * width - avg. number of bytes per tuple in the relation after the
236 * appropriate projections have been done (ie, output width)
237 * reltargetlist - List of Var nodes for the attributes we need to
238 * output from this relation (in no particular order)
239 * NOTE: in a child relation, may contain RowExprs
240 * pathlist - List of Path nodes, one for each potentially useful
241 * method of generating the relation
242 * cheapest_startup_path - the pathlist member with lowest startup cost
243 * (regardless of its ordering)
244 * cheapest_total_path - the pathlist member with lowest total cost
245 * (regardless of its ordering)
246 * cheapest_unique_path - for caching cheapest path to produce unique
247 * (no duplicates) output from relation
249 * If the relation is a base relation it will have these fields set:
251 * relid - RTE index (this is redundant with the relids field, but
252 * is provided for convenience of access)
253 * rtekind - distinguishes plain relation, subquery, or function RTE
254 * min_attr, max_attr - range of valid AttrNumbers for rel
255 * attr_needed - array of bitmapsets indicating the highest joinrel
256 * in which each attribute is needed; if bit 0 is set then
257 * the attribute is needed as part of final targetlist
258 * attr_widths - cache space for per-attribute width estimates;
259 * zero means not computed yet
260 * indexlist - list of IndexOptInfo nodes for relation's indexes
261 * (always NIL if it's not a table)
262 * pages - number of disk pages in relation (zero if not a table)
263 * tuples - number of tuples in relation (not considering restrictions)
264 * subplan - plan for subquery (NULL if it's not a subquery)
265 * subrtable - rangetable for subquery (NIL if it's not a subquery)
267 * Note: for a subquery, tuples and subplan are not set immediately
268 * upon creation of the RelOptInfo object; they are filled in when
269 * set_base_rel_pathlist processes the object.
271 * For otherrels that are appendrel members, these fields are filled
272 * in just as for a baserel.
274 * The presence of the remaining fields depends on the restrictions
275 * and joins that the relation participates in:
277 * baserestrictinfo - List of RestrictInfo nodes, containing info about
278 * each non-join qualification clause in which this relation
279 * participates (only used for base rels)
280 * baserestrictcost - Estimated cost of evaluating the baserestrictinfo
281 * clauses at a single tuple (only used for base rels)
282 * joininfo - List of RestrictInfo nodes, containing info about each
283 * join clause in which this relation participates (but
284 * note this excludes clauses that might be derivable from
285 * EquivalenceClasses)
286 * has_eclass_joins - flag that EquivalenceClass joins are possible
287 * index_outer_relids - only used for base rels; set of outer relids
288 * that participate in indexable joinclauses for this rel
289 * index_inner_paths - only used for base rels; list of InnerIndexscanInfo
290 * nodes showing best indexpaths for various subsets of
291 * index_outer_relids.
293 * Note: Keeping a restrictinfo list in the RelOptInfo is useful only for
294 * base rels, because for a join rel the set of clauses that are treated as
295 * restrict clauses varies depending on which sub-relations we choose to join.
296 * (For example, in a 3-base-rel join, a clause relating rels 1 and 2 must be
297 * treated as a restrictclause if we join {1} and {2 3} to make {1 2 3}; but
298 * if we join {1 2} and {3} then that clause will be a restrictclause in {1 2}
299 * and should not be processed again at the level of {1 2 3}.) Therefore,
300 * the restrictinfo list in the join case appears in individual JoinPaths
301 * (field joinrestrictinfo), not in the parent relation. But it's OK for
302 * the RelOptInfo to store the joininfo list, because that is the same
303 * for a given rel no matter how we form it.
305 * We store baserestrictcost in the RelOptInfo (for base relations) because
306 * we know we will need it at least once (to price the sequential scan)
307 * and may need it multiple times to price index scans.
310 typedef enum RelOptKind
314 RELOPT_OTHER_MEMBER_REL
317 typedef struct RelOptInfo
321 RelOptKind reloptkind;
323 /* all relations included in this RelOptInfo */
324 Relids relids; /* set of base relids (rangetable indexes) */
326 /* size estimates generated by planner */
327 double rows; /* estimated number of result tuples */
328 int width; /* estimated avg width of result tuples */
330 /* materialization information */
331 List *reltargetlist; /* needed Vars */
332 List *pathlist; /* Path structures */
333 struct Path *cheapest_startup_path;
334 struct Path *cheapest_total_path;
335 struct Path *cheapest_unique_path;
337 /* information about a base rel (not set for join rels!) */
339 RTEKind rtekind; /* RELATION, SUBQUERY, or FUNCTION */
340 AttrNumber min_attr; /* smallest attrno of rel (often <0) */
341 AttrNumber max_attr; /* largest attrno of rel */
342 Relids *attr_needed; /* array indexed [min_attr .. max_attr] */
343 int32 *attr_widths; /* array indexed [min_attr .. max_attr] */
347 struct Plan *subplan; /* if subquery */
348 List *subrtable; /* if subquery */
350 /* used by various scans and joins: */
351 List *baserestrictinfo; /* RestrictInfo structures (if base
353 QualCost baserestrictcost; /* cost of evaluating the above */
354 List *joininfo; /* RestrictInfo structures for join clauses
355 * involving this rel */
356 bool has_eclass_joins; /* T means joininfo is incomplete */
358 /* cached info about inner indexscan paths for relation: */
359 Relids index_outer_relids; /* other relids in indexable join
361 List *index_inner_paths; /* InnerIndexscanInfo nodes */
364 * Inner indexscans are not in the main pathlist because they are not
365 * usable except in specific join contexts. We use the index_inner_paths
366 * list just to avoid recomputing the best inner indexscan repeatedly for
367 * similar outer relations. See comments for InnerIndexscanInfo.
373 * Per-index information for planning/optimization
375 * Prior to Postgres 7.0, RelOptInfo was used to describe both relations
376 * and indexes, but that created confusion without actually doing anything
377 * useful. So now we have a separate IndexOptInfo struct for indexes.
379 * opfamily[], indexkeys[], opcintype[], fwdsortop[], revsortop[],
380 * and nulls_first[] each have ncolumns entries.
381 * Note: for historical reasons, the opfamily array has an extra entry
382 * that is always zero. Some code scans until it sees a zero entry,
383 * rather than looking at ncolumns.
385 * Zeroes in the indexkeys[] array indicate index columns that are
386 * expressions; there is one element in indexprs for each such column.
388 * For an unordered index, the sortop arrays contains zeroes. Note that
389 * fwdsortop[] and nulls_first[] describe the sort ordering of a forward
390 * indexscan; we can also consider a backward indexscan, which will
391 * generate sort order described by revsortop/!nulls_first.
393 * The indexprs and indpred expressions have been run through
394 * prepqual.c and eval_const_expressions() for ease of matching to
395 * WHERE clauses. indpred is in implicit-AND form.
397 typedef struct IndexOptInfo
401 Oid indexoid; /* OID of the index relation */
402 RelOptInfo *rel; /* back-link to index's table */
404 /* statistics from pg_class */
405 BlockNumber pages; /* number of disk pages in index */
406 double tuples; /* number of index tuples in index */
408 /* index descriptor information */
409 int ncolumns; /* number of columns in index */
410 Oid *opfamily; /* OIDs of operator families for columns */
411 int *indexkeys; /* column numbers of index's keys, or 0 */
412 Oid *opcintype; /* OIDs of opclass declared input data types */
413 Oid *fwdsortop; /* OIDs of sort operators for each column */
414 Oid *revsortop; /* OIDs of sort operators for backward scan */
415 bool *nulls_first; /* do NULLs come first in the sort order? */
416 Oid relam; /* OID of the access method (in pg_am) */
418 RegProcedure amcostestimate; /* OID of the access method's cost fcn */
420 List *indexprs; /* expressions for non-simple index columns */
421 List *indpred; /* predicate if a partial index, else NIL */
423 bool predOK; /* true if predicate matches query */
424 bool unique; /* true if a unique index */
425 bool amoptionalkey; /* can query omit key for the first column? */
426 bool amsearchnulls; /* can AM search for NULL index entries? */
433 * Whenever we can determine that a mergejoinable equality clause A = B is
434 * not delayed by any outer join, we create an EquivalenceClass containing
435 * the expressions A and B to record this knowledge. If we later find another
436 * equivalence B = C, we add C to the existing EquivalenceClass; this may
437 * require merging two existing EquivalenceClasses. At the end of the qual
438 * distribution process, we have sets of values that are known all transitively
439 * equal to each other, where "equal" is according to the rules of the btree
440 * operator family(s) shown in ec_opfamilies. (We restrict an EC to contain
441 * only equalities whose operators belong to the same set of opfamilies. This
442 * could probably be relaxed, but for now it's not worth the trouble, since
443 * nearly all equality operators belong to only one btree opclass anyway.)
445 * We also use EquivalenceClasses as the base structure for PathKeys, letting
446 * us represent knowledge about different sort orderings being equivalent.
447 * Since every PathKey must reference an EquivalenceClass, we will end up
448 * with single-member EquivalenceClasses whenever a sort key expression has
449 * not been equivalenced to anything else. It is also possible that such an
450 * EquivalenceClass will contain a volatile expression ("ORDER BY random()"),
451 * which is a case that can't arise otherwise since clauses containing
452 * volatile functions are never considered mergejoinable. We mark such
453 * EquivalenceClasses specially to prevent them from being merged with
454 * ordinary EquivalenceClasses. Also, for volatile expressions we have
455 * to be careful to match the EquivalenceClass to the correct targetlist
456 * entry: consider SELECT random() AS a, random() AS b ... ORDER BY b,a.
457 * So we record the SortGroupRef of the originating sort clause.
459 * We allow equality clauses appearing below the nullable side of an outer join
460 * to form EquivalenceClasses, but these have a slightly different meaning:
461 * the included values might be all NULL rather than all the same non-null
462 * values. See src/backend/optimizer/README for more on that point.
464 * NB: if ec_merged isn't NULL, this class has been merged into another, and
465 * should be ignored in favor of using the pointed-to class.
467 typedef struct EquivalenceClass
471 List *ec_opfamilies; /* btree operator family OIDs */
472 List *ec_members; /* list of EquivalenceMembers */
473 List *ec_sources; /* list of generating RestrictInfos */
474 List *ec_derives; /* list of derived RestrictInfos */
475 Relids ec_relids; /* all relids appearing in ec_members */
476 bool ec_has_const; /* any pseudoconstants in ec_members? */
477 bool ec_has_volatile; /* the (sole) member is a volatile expr */
478 bool ec_below_outer_join; /* equivalence applies below an OJ */
479 bool ec_broken; /* failed to generate needed clauses? */
480 Index ec_sortref; /* originating sortclause label, or 0 */
481 struct EquivalenceClass *ec_merged; /* set if merged into another EC */
485 * If an EC contains a const and isn't below-outer-join, any PathKey depending
486 * on it must be redundant, since there's only one possible value of the key.
488 #define EC_MUST_BE_REDUNDANT(eclass) \
489 ((eclass)->ec_has_const && !(eclass)->ec_below_outer_join)
492 * EquivalenceMember - one member expression of an EquivalenceClass
494 * em_is_child signifies that this element was built by transposing a member
495 * for an inheritance parent relation to represent the corresponding expression
496 * on an inheritance child. The element should be ignored for all purposes
497 * except constructing inner-indexscan paths for the child relation. (Other
498 * types of join are driven from transposed joininfo-list entries.) Note
499 * that the EC's ec_relids field does NOT include the child relation.
501 * em_datatype is usually the same as exprType(em_expr), but can be
502 * different when dealing with a binary-compatible opfamily; in particular
503 * anyarray_ops would never work without this. Use em_datatype when
504 * looking up a specific btree operator to work with this expression.
506 typedef struct EquivalenceMember
510 Expr *em_expr; /* the expression represented */
511 Relids em_relids; /* all relids appearing in em_expr */
512 bool em_is_const; /* expression is pseudoconstant? */
513 bool em_is_child; /* derived version for a child relation? */
514 Oid em_datatype; /* the "nominal type" used by the opfamily */
520 * The sort ordering of a path is represented by a list of PathKey nodes.
521 * An empty list implies no known ordering. Otherwise the first item
522 * represents the primary sort key, the second the first secondary sort key,
523 * etc. The value being sorted is represented by linking to an
524 * EquivalenceClass containing that value and including pk_opfamily among its
525 * ec_opfamilies. This is a convenient method because it makes it trivial
526 * to detect equivalent and closely-related orderings. (See optimizer/README
527 * for more information.)
529 * Note: pk_strategy is either BTLessStrategyNumber (for ASC) or
530 * BTGreaterStrategyNumber (for DESC). We assume that all ordering-capable
531 * index types will use btree-compatible strategy numbers.
534 typedef struct PathKey
538 EquivalenceClass *pk_eclass; /* the value that is ordered */
539 Oid pk_opfamily; /* btree opfamily defining the ordering */
540 int pk_strategy; /* sort direction (ASC or DESC) */
541 bool pk_nulls_first; /* do NULLs come before normal values? */
545 * Type "Path" is used as-is for sequential-scan paths. For other
546 * path types it is the first component of a larger struct.
548 * Note: "pathtype" is the NodeTag of the Plan node we could build from this
549 * Path. It is partially redundant with the Path's NodeTag, but allows us
550 * to use the same Path type for multiple Plan types where there is no need
551 * to distinguish the Plan type during path processing.
558 NodeTag pathtype; /* tag identifying scan/join method */
560 RelOptInfo *parent; /* the relation this path can build */
562 /* estimated execution costs for path (see costsize.c for more info) */
563 Cost startup_cost; /* cost expended before fetching any tuples */
564 Cost total_cost; /* total cost (assuming all tuples fetched) */
566 List *pathkeys; /* sort ordering of path's output */
567 /* pathkeys is a List of PathKey nodes; see above */
571 * IndexPath represents an index scan over a single index.
573 * 'indexinfo' is the index to be scanned.
575 * 'indexclauses' is a list of index qualification clauses, with implicit
576 * AND semantics across the list. Each clause is a RestrictInfo node from
577 * the query's WHERE or JOIN conditions.
579 * 'indexquals' has the same structure as 'indexclauses', but it contains
580 * the actual indexqual conditions that can be used with the index.
581 * In simple cases this is identical to 'indexclauses', but when special
582 * indexable operators appear in 'indexclauses', they are replaced by the
583 * derived indexscannable conditions in 'indexquals'.
585 * 'isjoininner' is TRUE if the path is a nestloop inner scan (that is,
586 * some of the index conditions are join rather than restriction clauses).
587 * Note that the path costs will be calculated differently from a plain
588 * indexscan in this case, and in addition there's a special 'rows' value
589 * different from the parent RelOptInfo's (see below).
591 * 'indexscandir' is one of:
592 * ForwardScanDirection: forward scan of an ordered index
593 * BackwardScanDirection: backward scan of an ordered index
594 * NoMovementScanDirection: scan of an unordered index, or don't care
595 * (The executor doesn't care whether it gets ForwardScanDirection or
596 * NoMovementScanDirection for an indexscan, but the planner wants to
597 * distinguish ordered from unordered indexes for building pathkeys.)
599 * 'indextotalcost' and 'indexselectivity' are saved in the IndexPath so that
600 * we need not recompute them when considering using the same index in a
601 * bitmap index/heap scan (see BitmapHeapPath). The costs of the IndexPath
602 * itself represent the costs of an IndexScan plan type.
604 * 'rows' is the estimated result tuple count for the indexscan. This
605 * is the same as path.parent->rows for a simple indexscan, but it is
606 * different for a nestloop inner scan, because the additional indexquals
607 * coming from join clauses make the scan more selective than the parent
608 * rel's restrict clauses alone would do.
611 typedef struct IndexPath
614 IndexOptInfo *indexinfo;
618 ScanDirection indexscandir;
620 Selectivity indexselectivity;
621 double rows; /* estimated number of result tuples */
625 * BitmapHeapPath represents one or more indexscans that generate TID bitmaps
626 * instead of directly accessing the heap, followed by AND/OR combinations
627 * to produce a single bitmap, followed by a heap scan that uses the bitmap.
628 * Note that the output is always considered unordered, since it will come
629 * out in physical heap order no matter what the underlying indexes did.
631 * The individual indexscans are represented by IndexPath nodes, and any
632 * logic on top of them is represented by a tree of BitmapAndPath and
633 * BitmapOrPath nodes. Notice that we can use the same IndexPath node both
634 * to represent a regular IndexScan plan, and as the child of a BitmapHeapPath
635 * that represents scanning the same index using a BitmapIndexScan. The
636 * startup_cost and total_cost figures of an IndexPath always represent the
637 * costs to use it as a regular IndexScan. The costs of a BitmapIndexScan
638 * can be computed using the IndexPath's indextotalcost and indexselectivity.
640 * BitmapHeapPaths can be nestloop inner indexscans. The isjoininner and
641 * rows fields serve the same purpose as for plain IndexPaths.
643 typedef struct BitmapHeapPath
646 Path *bitmapqual; /* IndexPath, BitmapAndPath, BitmapOrPath */
647 bool isjoininner; /* T if it's a nestloop inner scan */
648 double rows; /* estimated number of result tuples */
652 * BitmapAndPath represents a BitmapAnd plan node; it can only appear as
653 * part of the substructure of a BitmapHeapPath. The Path structure is
654 * a bit more heavyweight than we really need for this, but for simplicity
655 * we make it a derivative of Path anyway.
657 typedef struct BitmapAndPath
660 List *bitmapquals; /* IndexPaths and BitmapOrPaths */
661 Selectivity bitmapselectivity;
665 * BitmapOrPath represents a BitmapOr plan node; it can only appear as
666 * part of the substructure of a BitmapHeapPath. The Path structure is
667 * a bit more heavyweight than we really need for this, but for simplicity
668 * we make it a derivative of Path anyway.
670 typedef struct BitmapOrPath
673 List *bitmapquals; /* IndexPaths and BitmapAndPaths */
674 Selectivity bitmapselectivity;
678 * TidPath represents a scan by TID
680 * tidquals is an implicitly OR'ed list of qual expressions of the form
681 * "CTID = pseudoconstant" or "CTID = ANY(pseudoconstant_array)".
682 * Note they are bare expressions, not RestrictInfos.
684 typedef struct TidPath
687 List *tidquals; /* qual(s) involving CTID = something */
691 * AppendPath represents an Append plan, ie, successive execution of
692 * several member plans.
694 * Note: it is possible for "subpaths" to contain only one, or even no,
695 * elements. These cases are optimized during create_append_plan.
696 * In particular, an AppendPath with no subpaths is a "dummy" path that
697 * is created to represent the case that a relation is provably empty.
699 typedef struct AppendPath
702 List *subpaths; /* list of component Paths */
705 #define IS_DUMMY_PATH(p) \
706 (IsA((p), AppendPath) && ((AppendPath *) (p))->subpaths == NIL)
709 * ResultPath represents use of a Result plan node to compute a variable-free
710 * targetlist with no underlying tables (a "SELECT expressions" query).
711 * The query could have a WHERE clause, too, represented by "quals".
713 * Note that quals is a list of bare clauses, not RestrictInfos.
715 typedef struct ResultPath
722 * MaterialPath represents use of a Material plan node, i.e., caching of
723 * the output of its subpath. This is used when the subpath is expensive
724 * and needs to be scanned repeatedly, or when we need mark/restore ability
725 * and the subpath doesn't have it.
727 typedef struct MaterialPath
734 * UniquePath represents elimination of distinct rows from the output of
737 * This is unlike the other Path nodes in that it can actually generate
738 * different plans: either hash-based or sort-based implementation, or a
739 * no-op if the input path can be proven distinct already. The decision
740 * is sufficiently localized that it's not worth having separate Path node
741 * types. (Note: in the no-op case, we could eliminate the UniquePath node
742 * entirely and just return the subpath; but it's convenient to have a
743 * UniquePath in the path tree to signal upper-level routines that the input
744 * is known distinct.)
748 UNIQUE_PATH_NOOP, /* input is known unique already */
749 UNIQUE_PATH_HASH, /* use hashing */
750 UNIQUE_PATH_SORT /* use sorting */
753 typedef struct UniquePath
757 UniquePathMethod umethod;
758 List *in_operators; /* equality operators of the IN clause */
759 List *uniq_exprs; /* expressions to be made unique */
760 double rows; /* estimated number of result tuples */
764 * All join-type paths share these fields.
767 typedef struct JoinPath
773 Path *outerjoinpath; /* path for the outer side of the join */
774 Path *innerjoinpath; /* path for the inner side of the join */
776 List *joinrestrictinfo; /* RestrictInfos to apply to join */
779 * See the notes for RelOptInfo to understand why joinrestrictinfo is
780 * needed in JoinPath, and can't be merged into the parent RelOptInfo.
785 * A nested-loop path needs no special fields.
788 typedef JoinPath NestPath;
791 * A mergejoin path has these fields.
793 * path_mergeclauses lists the clauses (in the form of RestrictInfos)
794 * that will be used in the merge.
796 * Note that the mergeclauses are a subset of the parent relation's
797 * restriction-clause list. Any join clauses that are not mergejoinable
798 * appear only in the parent's restrict list, and must be checked by a
799 * qpqual at execution time.
801 * outersortkeys (resp. innersortkeys) is NIL if the outer path
802 * (resp. inner path) is already ordered appropriately for the
803 * mergejoin. If it is not NIL then it is a PathKeys list describing
804 * the ordering that must be created by an explicit sort step.
807 typedef struct MergePath
810 List *path_mergeclauses; /* join clauses to be used for merge */
811 List *outersortkeys; /* keys for explicit sort, if any */
812 List *innersortkeys; /* keys for explicit sort, if any */
816 * A hashjoin path has these fields.
818 * The remarks above for mergeclauses apply for hashclauses as well.
820 * Hashjoin does not care what order its inputs appear in, so we have
821 * no need for sortkeys.
824 typedef struct HashPath
827 List *path_hashclauses; /* join clauses used for hashing */
831 * Restriction clause info.
833 * We create one of these for each AND sub-clause of a restriction condition
834 * (WHERE or JOIN/ON clause). Since the restriction clauses are logically
835 * ANDed, we can use any one of them or any subset of them to filter out
836 * tuples, without having to evaluate the rest. The RestrictInfo node itself
837 * stores data used by the optimizer while choosing the best query plan.
839 * If a restriction clause references a single base relation, it will appear
840 * in the baserestrictinfo list of the RelOptInfo for that base rel.
842 * If a restriction clause references more than one base rel, it will
843 * appear in the joininfo list of every RelOptInfo that describes a strict
844 * subset of the base rels mentioned in the clause. The joininfo lists are
845 * used to drive join tree building by selecting plausible join candidates.
846 * The clause cannot actually be applied until we have built a join rel
847 * containing all the base rels it references, however.
849 * When we construct a join rel that includes all the base rels referenced
850 * in a multi-relation restriction clause, we place that clause into the
851 * joinrestrictinfo lists of paths for the join rel, if neither left nor
852 * right sub-path includes all base rels referenced in the clause. The clause
853 * will be applied at that join level, and will not propagate any further up
854 * the join tree. (Note: the "predicate migration" code was once intended to
855 * push restriction clauses up and down the plan tree based on evaluation
856 * costs, but it's dead code and is unlikely to be resurrected in the
857 * foreseeable future.)
859 * Note that in the presence of more than two rels, a multi-rel restriction
860 * might reach different heights in the join tree depending on the join
861 * sequence we use. So, these clauses cannot be associated directly with
862 * the join RelOptInfo, but must be kept track of on a per-join-path basis.
864 * RestrictInfos that represent equivalence conditions (i.e., mergejoinable
865 * equalities that are not outerjoin-delayed) are handled a bit differently.
866 * Initially we attach them to the EquivalenceClasses that are derived from
867 * them. When we construct a scan or join path, we look through all the
868 * EquivalenceClasses and generate derived RestrictInfos representing the
869 * minimal set of conditions that need to be checked for this particular scan
870 * or join to enforce that all members of each EquivalenceClass are in fact
871 * equal in all rows emitted by the scan or join.
873 * When dealing with outer joins we have to be very careful about pushing qual
874 * clauses up and down the tree. An outer join's own JOIN/ON conditions must
875 * be evaluated exactly at that join node, unless they are "degenerate"
876 * conditions that reference only Vars from the nullable side of the join.
877 * Quals appearing in WHERE or in a JOIN above the outer join cannot be pushed
878 * down below the outer join, if they reference any nullable Vars.
879 * RestrictInfo nodes contain a flag to indicate whether a qual has been
880 * pushed down to a lower level than its original syntactic placement in the
881 * join tree would suggest. If an outer join prevents us from pushing a qual
882 * down to its "natural" semantic level (the level associated with just the
883 * base rels used in the qual) then we mark the qual with a "required_relids"
884 * value including more than just the base rels it actually uses. By
885 * pretending that the qual references all the rels required to form the outer
886 * join, we prevent it from being evaluated below the outer join's joinrel.
887 * When we do form the outer join's joinrel, we still need to distinguish
888 * those quals that are actually in that join's JOIN/ON condition from those
889 * that appeared elsewhere in the tree and were pushed down to the join rel
890 * because they used no other rels. That's what the is_pushed_down flag is
891 * for; it tells us that a qual is not an OUTER JOIN qual for the set of base
892 * rels listed in required_relids. A clause that originally came from WHERE
893 * or an INNER JOIN condition will *always* have its is_pushed_down flag set.
894 * It's possible for an OUTER JOIN clause to be marked is_pushed_down too,
895 * if we decide that it can be pushed down into the nullable side of the join.
896 * In that case it acts as a plain filter qual for wherever it gets evaluated.
897 * (In short, is_pushed_down is only false for non-degenerate outer join
898 * conditions. Possibly we should rename it to reflect that meaning?)
900 * RestrictInfo nodes also contain an outerjoin_delayed flag, which is true
901 * if the clause's applicability must be delayed due to any outer joins
902 * appearing below its own syntactic level (ie, it references any Vars from
903 * the nullable side of any lower outer join).
905 * In general, the referenced clause might be arbitrarily complex. The
906 * kinds of clauses we can handle as indexscan quals, mergejoin clauses,
907 * or hashjoin clauses are limited (e.g., no volatile functions). The code
908 * for each kind of path is responsible for identifying the restrict clauses
909 * it can use and ignoring the rest. Clauses not implemented by an indexscan,
910 * mergejoin, or hashjoin will be placed in the plan qual or joinqual field
911 * of the finished Plan node, where they will be enforced by general-purpose
912 * qual-expression-evaluation code. (But we are still entitled to count
913 * their selectivity when estimating the result tuple count, if we
914 * can guess what it is...)
916 * When the referenced clause is an OR clause, we generate a modified copy
917 * in which additional RestrictInfo nodes are inserted below the top-level
918 * OR/AND structure. This is a convenience for OR indexscan processing:
919 * indexquals taken from either the top level or an OR subclause will have
920 * associated RestrictInfo nodes.
922 * The can_join flag is set true if the clause looks potentially useful as
923 * a merge or hash join clause, that is if it is a binary opclause with
924 * nonoverlapping sets of relids referenced in the left and right sides.
925 * (Whether the operator is actually merge or hash joinable isn't checked,
928 * The pseudoconstant flag is set true if the clause contains no Vars of
929 * the current query level and no volatile functions. Such a clause can be
930 * pulled out and used as a one-time qual in a gating Result node. We keep
931 * pseudoconstant clauses in the same lists as other RestrictInfos so that
932 * the regular clause-pushing machinery can assign them to the correct join
933 * level, but they need to be treated specially for cost and selectivity
934 * estimates. Note that a pseudoconstant clause can never be an indexqual
935 * or merge or hash join clause, so it's of no interest to large parts of
938 * When join clauses are generated from EquivalenceClasses, there may be
939 * several equally valid ways to enforce join equivalence, of which we need
940 * apply only one. We mark clauses of this kind by setting parent_ec to
941 * point to the generating EquivalenceClass. Multiple clauses with the same
942 * parent_ec in the same join are redundant.
945 typedef struct RestrictInfo
949 Expr *clause; /* the represented clause of WHERE or JOIN */
951 bool is_pushed_down; /* TRUE if clause was pushed down in level */
953 bool outerjoin_delayed; /* TRUE if delayed by lower outer join */
955 bool can_join; /* see comment above */
957 bool pseudoconstant; /* see comment above */
959 /* The set of relids (varnos) actually referenced in the clause: */
960 Relids clause_relids;
962 /* The set of relids required to evaluate the clause: */
963 Relids required_relids;
965 /* These fields are set for any binary opclause: */
966 Relids left_relids; /* relids in left side of clause */
967 Relids right_relids; /* relids in right side of clause */
969 /* This field is NULL unless clause is an OR clause: */
970 Expr *orclause; /* modified clause with RestrictInfos */
972 /* This field is NULL unless clause is potentially redundant: */
973 EquivalenceClass *parent_ec; /* generating EquivalenceClass */
975 /* cache space for cost and selectivity */
976 QualCost eval_cost; /* eval cost of clause; -1 if not yet set */
977 Selectivity this_selec; /* selectivity; -1 if not yet set */
979 /* valid if clause is mergejoinable, else NIL */
980 List *mergeopfamilies; /* opfamilies containing clause operator */
982 /* cache space for mergeclause processing; NULL if not yet set */
983 EquivalenceClass *left_ec; /* EquivalenceClass containing lefthand */
984 EquivalenceClass *right_ec; /* EquivalenceClass containing righthand */
985 EquivalenceMember *left_em; /* EquivalenceMember for lefthand */
986 EquivalenceMember *right_em; /* EquivalenceMember for righthand */
987 List *scansel_cache; /* list of MergeScanSelCache structs */
989 /* transient workspace for use while considering a specific join path */
990 bool outer_is_left; /* T = outer var on left, F = on right */
992 /* valid if clause is hashjoinable, else InvalidOid: */
993 Oid hashjoinoperator; /* copy of clause operator */
995 /* cache space for hashclause processing; -1 if not yet set */
996 Selectivity left_bucketsize; /* avg bucketsize of left side */
997 Selectivity right_bucketsize; /* avg bucketsize of right side */
1001 * Since mergejoinscansel() is a relatively expensive function, and would
1002 * otherwise be invoked many times while planning a large join tree,
1003 * we go out of our way to cache its results. Each mergejoinable
1004 * RestrictInfo carries a list of the specific sort orderings that have
1005 * been considered for use with it, and the resulting selectivities.
1007 typedef struct MergeScanSelCache
1009 /* Ordering details (cache lookup key) */
1010 Oid opfamily; /* btree opfamily defining the ordering */
1011 int strategy; /* sort direction (ASC or DESC) */
1012 bool nulls_first; /* do NULLs come before normal values? */
1014 Selectivity leftstartsel; /* first-join fraction for clause left side */
1015 Selectivity leftendsel; /* last-join fraction for clause left side */
1016 Selectivity rightstartsel; /* first-join fraction for clause right side */
1017 Selectivity rightendsel; /* last-join fraction for clause right side */
1018 } MergeScanSelCache;
1021 * Inner indexscan info.
1023 * An inner indexscan is one that uses one or more joinclauses as index
1024 * conditions (perhaps in addition to plain restriction clauses). So it
1025 * can only be used as the inner path of a nestloop join where the outer
1026 * relation includes all other relids appearing in those joinclauses.
1027 * The set of usable joinclauses, and thus the best inner indexscan,
1028 * thus varies depending on which outer relation we consider; so we have
1029 * to recompute the best such paths for every join. To avoid lots of
1030 * redundant computation, we cache the results of such searches. For
1031 * each relation we compute the set of possible otherrelids (all relids
1032 * appearing in joinquals that could become indexquals for this table).
1033 * Two outer relations whose relids have the same intersection with this
1034 * set will have the same set of available joinclauses and thus the same
1035 * best inner indexscans for the inner relation. By taking the intersection
1036 * before scanning the cache, we avoid recomputing when considering
1037 * join rels that differ only by the inclusion of irrelevant other rels.
1039 * The search key also includes a bool showing whether the join being
1040 * considered is an outer join. Since we constrain the join order for
1041 * outer joins, I believe that this bool can only have one possible value
1042 * for any particular lookup key; but store it anyway to avoid confusion.
1045 typedef struct InnerIndexscanInfo
1048 /* The lookup key: */
1049 Relids other_relids; /* a set of relevant other relids */
1050 bool isouterjoin; /* true if join is outer */
1051 /* Best paths for this lookup key (NULL if no available indexscans): */
1052 Path *cheapest_startup_innerpath; /* cheapest startup cost */
1053 Path *cheapest_total_innerpath; /* cheapest total cost */
1054 } InnerIndexscanInfo;
1057 * "Flattened SubLinks"
1059 * When we pull an IN or EXISTS SubLink up into the parent query, the
1060 * join conditions extracted from the IN/EXISTS clause need to be specially
1061 * treated in distribute_qual_to_rels processing. We handle this by
1062 * wrapping such expressions in a FlattenedSubLink node that identifies
1063 * the join they come from. The FlattenedSubLink node is discarded after
1064 * distribute_qual_to_rels, having served its purpose.
1066 * Although the planner treats this as an expression node type, it is not
1067 * recognized by the parser or executor, so we declare it here rather than
1071 typedef struct FlattenedSubLink
1074 JoinType jointype; /* must be JOIN_SEMI or JOIN_ANTI */
1075 Relids lefthand; /* base relids treated as syntactic LHS */
1076 Relids righthand; /* base relids syntactically within RHS */
1077 Expr *quals; /* join quals (in explicit-AND format) */
1081 * "Special join" info.
1083 * One-sided outer joins constrain the order of joining partially but not
1084 * completely. We flatten such joins into the planner's top-level list of
1085 * relations to join, but record information about each outer join in a
1086 * SpecialJoinInfo struct. These structs are kept in the PlannerInfo node's
1089 * Similarly, semijoins and antijoins created by flattening IN (subselect)
1090 * and EXISTS(subselect) clauses create partial constraints on join order.
1091 * These are likewise recorded in SpecialJoinInfo structs.
1093 * We make SpecialJoinInfos for FULL JOINs even though there is no flexibility
1094 * of planning for them, because this simplifies make_join_rel()'s API.
1096 * min_lefthand and min_righthand are the sets of base relids that must be
1097 * available on each side when performing the special join. lhs_strict is
1098 * true if the special join's condition cannot succeed when the LHS variables
1099 * are all NULL (this means that an outer join can commute with upper-level
1100 * outer joins even if it appears in their RHS). We don't bother to set
1101 * lhs_strict for FULL JOINs, however.
1103 * It is not valid for either min_lefthand or min_righthand to be empty sets;
1104 * if they were, this would break the logic that enforces join order.
1106 * syn_lefthand and syn_righthand are the sets of base relids that are
1107 * syntactically below this special join. (These are needed to help compute
1108 * min_lefthand and min_righthand for higher joins.)
1110 * delay_upper_joins is set TRUE if we detect a pushed-down clause that has
1111 * to be evaluated after this join is formed (because it references the RHS).
1112 * Any outer joins that have such a clause and this join in their RHS cannot
1113 * commute with this join, because that would leave noplace to check the
1114 * pushed-down clause. (We don't track this for FULL JOINs, either.)
1116 * join_quals is an implicit-AND list of the quals syntactically associated
1117 * with the join (they may or may not end up being applied at the join level).
1118 * This is just a side list and does not drive actual application of quals.
1119 * For JOIN_SEMI joins, this is cleared to NIL in create_unique_path() if
1120 * the join is found not to be suitable for a uniqueify-the-RHS plan.
1122 * jointype is never JOIN_RIGHT; a RIGHT JOIN is handled by switching
1123 * the inputs to make it a LEFT JOIN. So the allowed values of jointype
1124 * in a join_info_list member are only LEFT, FULL, SEMI, or ANTI.
1126 * For purposes of join selectivity estimation, we create transient
1127 * SpecialJoinInfo structures for regular inner joins; so it is possible
1128 * to have jointype == JOIN_INNER in such a structure, even though this is
1129 * not allowed within join_info_list. Note that lhs_strict, delay_upper_joins,
1130 * and join_quals are not set meaningfully for such structs.
1133 typedef struct SpecialJoinInfo
1136 Relids min_lefthand; /* base relids in minimum LHS for join */
1137 Relids min_righthand; /* base relids in minimum RHS for join */
1138 Relids syn_lefthand; /* base relids syntactically within LHS */
1139 Relids syn_righthand; /* base relids syntactically within RHS */
1140 JoinType jointype; /* always INNER, LEFT, FULL, SEMI, or ANTI */
1141 bool lhs_strict; /* joinclause is strict for some LHS rel */
1142 bool delay_upper_joins; /* can't commute with upper RHS */
1143 List *join_quals; /* join quals, in implicit-AND list format */
1147 * Append-relation info.
1149 * When we expand an inheritable table or a UNION-ALL subselect into an
1150 * "append relation" (essentially, a list of child RTEs), we build an
1151 * AppendRelInfo for each child RTE. The list of AppendRelInfos indicates
1152 * which child RTEs must be included when expanding the parent, and each
1153 * node carries information needed to translate Vars referencing the parent
1154 * into Vars referencing that child.
1156 * These structs are kept in the PlannerInfo node's append_rel_list.
1157 * Note that we just throw all the structs into one list, and scan the
1158 * whole list when desiring to expand any one parent. We could have used
1159 * a more complex data structure (eg, one list per parent), but this would
1160 * be harder to update during operations such as pulling up subqueries,
1161 * and not really any easier to scan. Considering that typical queries
1162 * will not have many different append parents, it doesn't seem worthwhile
1163 * to complicate things.
1165 * Note: after completion of the planner prep phase, any given RTE is an
1166 * append parent having entries in append_rel_list if and only if its
1167 * "inh" flag is set. We clear "inh" for plain tables that turn out not
1168 * to have inheritance children, and (in an abuse of the original meaning
1169 * of the flag) we set "inh" for subquery RTEs that turn out to be
1170 * flattenable UNION ALL queries. This lets us avoid useless searches
1171 * of append_rel_list.
1173 * Note: the data structure assumes that append-rel members are single
1174 * baserels. This is OK for inheritance, but it prevents us from pulling
1175 * up a UNION ALL member subquery if it contains a join. While that could
1176 * be fixed with a more complex data structure, at present there's not much
1177 * point because no improvement in the plan could result.
1180 typedef struct AppendRelInfo
1185 * These fields uniquely identify this append relationship. There can be
1186 * (in fact, always should be) multiple AppendRelInfos for the same
1187 * parent_relid, but never more than one per child_relid, since a given
1188 * RTE cannot be a child of more than one append parent.
1190 Index parent_relid; /* RT index of append parent rel */
1191 Index child_relid; /* RT index of append child rel */
1194 * For an inheritance appendrel, the parent and child are both regular
1195 * relations, and we store their rowtype OIDs here for use in translating
1196 * whole-row Vars. For a UNION-ALL appendrel, the parent and child are
1197 * both subqueries with no named rowtype, and we store InvalidOid here.
1199 Oid parent_reltype; /* OID of parent's composite type */
1200 Oid child_reltype; /* OID of child's composite type */
1203 * The N'th element of this list is the integer column number of the child
1204 * column corresponding to the N'th column of the parent. A list element
1205 * is zero if it corresponds to a dropped column of the parent (this is
1206 * only possible for inheritance cases, not UNION ALL).
1208 List *col_mappings; /* list of child attribute numbers */
1211 * The N'th element of this list is a Var or expression representing the
1212 * child column corresponding to the N'th column of the parent. This is
1213 * used to translate Vars referencing the parent rel into references to
1214 * the child. A list element is NULL if it corresponds to a dropped
1215 * column of the parent (this is only possible for inheritance cases, not
1218 * This might seem redundant with the col_mappings data, but it is handy
1219 * because flattening of sub-SELECTs that are members of a UNION ALL will
1220 * cause changes in the expressions that need to be substituted for a
1221 * parent Var. Adjusting this data structure lets us track what really
1222 * needs to be substituted.
1224 * Notice we only store entries for user columns (attno > 0). Whole-row
1225 * Vars are special-cased, and system columns (attno < 0) need no special
1226 * translation since their attnos are the same for all tables.
1228 * Caution: the Vars have varlevelsup = 0. Be careful to adjust as needed
1229 * when copying into a subquery.
1231 List *translated_vars; /* Expressions in the child's Vars */
1234 * We store the parent table's OID here for inheritance, or InvalidOid for
1235 * UNION ALL. This is only needed to help in generating error messages if
1236 * an attempt is made to reference a dropped parent column.
1238 Oid parent_reloid; /* OID of parent relation */
1242 * glob->paramlist keeps track of the PARAM_EXEC slots that we have decided
1243 * we need for the query. At runtime these slots are used to pass values
1244 * either down into subqueries (for outer references in subqueries) or up out
1245 * of subqueries (for the results of a subplan). The n'th entry in the list
1246 * (n counts from 0) corresponds to Param->paramid = n.
1248 * Each paramlist item shows the absolute query level it is associated with,
1249 * where the outermost query is level 1 and nested subqueries have higher
1250 * numbers. The item the parameter slot represents can be one of three kinds:
1252 * A Var: the slot represents a variable of that level that must be passed
1253 * down because subqueries have outer references to it. The varlevelsup
1254 * value in the Var will always be zero.
1256 * An Aggref (with an expression tree representing its argument): the slot
1257 * represents an aggregate expression that is an outer reference for some
1258 * subquery. The Aggref itself has agglevelsup = 0, and its argument tree
1259 * is adjusted to match in level.
1261 * A Param: the slot holds the result of a subplan (it is a setParam item
1262 * for that subplan). The absolute level shown for such items corresponds
1263 * to the parent query of the subplan.
1265 * Note: we detect duplicate Var parameters and coalesce them into one slot,
1266 * but we do not do this for Aggref or Param slots.
1268 typedef struct PlannerParamItem
1272 Node *item; /* the Var, Aggref, or Param */
1273 Index abslevel; /* its absolute query level */
1276 #endif /* RELATION_H */