mirror of
https://github.com/postgres/postgres.git
synced 2025-11-06 07:49:08 +03:00
pgindent run for 9.4
This includes removing tabs after periods in C comments, which was applied to back branches, so this change should not effect backpatching.
This commit is contained in:
@@ -128,7 +128,7 @@ typedef struct Query
|
||||
|
||||
List *targetList; /* target list (of TargetEntry) */
|
||||
|
||||
List *withCheckOptions; /* a list of WithCheckOption's */
|
||||
List *withCheckOptions; /* a list of WithCheckOption's */
|
||||
|
||||
List *returningList; /* return-values list (of TargetEntry) */
|
||||
|
||||
@@ -159,7 +159,7 @@ typedef struct Query
|
||||
* Supporting data structures for Parse Trees
|
||||
*
|
||||
* Most of these node types appear in raw parsetrees output by the grammar,
|
||||
* and get transformed to something else by the analyzer. A few of them
|
||||
* and get transformed to something else by the analyzer. A few of them
|
||||
* are used as-is in transformed querytrees.
|
||||
****************************************************************************/
|
||||
|
||||
@@ -173,7 +173,7 @@ typedef struct Query
|
||||
* be prespecified in typemod, otherwise typemod is unused.
|
||||
*
|
||||
* If pct_type is TRUE, then names is actually a field name and we look up
|
||||
* the type of that field. Otherwise (the normal case), names is a type
|
||||
* the type of that field. Otherwise (the normal case), names is a type
|
||||
* name possibly qualified with schema and database name.
|
||||
*/
|
||||
typedef struct TypeName
|
||||
@@ -192,7 +192,7 @@ typedef struct TypeName
|
||||
/*
|
||||
* ColumnRef - specifies a reference to a column, or possibly a whole tuple
|
||||
*
|
||||
* The "fields" list must be nonempty. It can contain string Value nodes
|
||||
* The "fields" list must be nonempty. It can contain string Value nodes
|
||||
* (representing names) and A_Star nodes (representing occurrence of a '*').
|
||||
* Currently, A_Star must appear only as the last list element --- the grammar
|
||||
* is responsible for enforcing this!
|
||||
@@ -468,7 +468,7 @@ typedef struct RangeSubselect
|
||||
* RangeFunction - function call appearing in a FROM clause
|
||||
*
|
||||
* functions is a List because we use this to represent the construct
|
||||
* ROWS FROM(func1(...), func2(...), ...). Each element of this list is a
|
||||
* ROWS FROM(func1(...), func2(...), ...). Each element of this list is a
|
||||
* two-element sublist, the first element being the untransformed function
|
||||
* call tree, and the second element being a possibly-empty list of ColumnDef
|
||||
* nodes representing any columndef list attached to that function within the
|
||||
@@ -497,7 +497,7 @@ typedef struct RangeFunction
|
||||
* in either "raw" form (an untransformed parse tree) or "cooked" form
|
||||
* (a post-parse-analysis, executable expression tree), depending on
|
||||
* how this ColumnDef node was created (by parsing, or by inheritance
|
||||
* from an existing relation). We should never have both in the same node!
|
||||
* from an existing relation). We should never have both in the same node!
|
||||
*
|
||||
* Similarly, we may have a COLLATE specification in either raw form
|
||||
* (represented as a CollateClause with arg==NULL) or cooked form
|
||||
@@ -569,7 +569,7 @@ typedef struct IndexElem
|
||||
/*
|
||||
* DefElem - a generic "name = value" option definition
|
||||
*
|
||||
* In some contexts the name can be qualified. Also, certain SQL commands
|
||||
* In some contexts the name can be qualified. Also, certain SQL commands
|
||||
* allow a SET/ADD/DROP action to be attached to option settings, so it's
|
||||
* convenient to carry a field for that too. (Note: currently, it is our
|
||||
* practice that the grammar allows namespace and action only in statements
|
||||
@@ -597,7 +597,7 @@ typedef struct DefElem
|
||||
* LockingClause - raw representation of FOR [NO KEY] UPDATE/[KEY] SHARE
|
||||
* options
|
||||
*
|
||||
* Note: lockedRels == NIL means "all relations in query". Otherwise it
|
||||
* Note: lockedRels == NIL means "all relations in query". Otherwise it
|
||||
* is a list of RangeVar nodes. (We use RangeVar mainly because it carries
|
||||
* a location field --- currently, parse analysis insists on unqualified
|
||||
* names in LockingClause.)
|
||||
@@ -661,8 +661,8 @@ typedef struct XmlSerialize
|
||||
*
|
||||
* In RELATION RTEs, the colnames in both alias and eref are indexed by
|
||||
* physical attribute number; this means there must be colname entries for
|
||||
* dropped columns. When building an RTE we insert empty strings ("") for
|
||||
* dropped columns. Note however that a stored rule may have nonempty
|
||||
* dropped columns. When building an RTE we insert empty strings ("") for
|
||||
* dropped columns. Note however that a stored rule may have nonempty
|
||||
* colnames for columns dropped since the rule was created (and for that
|
||||
* matter the colnames might be out of date due to column renamings).
|
||||
* The same comments apply to FUNCTION RTEs when a function's return type
|
||||
@@ -670,9 +670,9 @@ typedef struct XmlSerialize
|
||||
*
|
||||
* In JOIN RTEs, the colnames in both alias and eref are one-to-one with
|
||||
* joinaliasvars entries. A JOIN RTE will omit columns of its inputs when
|
||||
* those columns are known to be dropped at parse time. Again, however,
|
||||
* those columns are known to be dropped at parse time. Again, however,
|
||||
* a stored rule might contain entries for columns dropped since the rule
|
||||
* was created. (This is only possible for columns not actually referenced
|
||||
* was created. (This is only possible for columns not actually referenced
|
||||
* in the rule.) When loading a stored rule, we replace the joinaliasvars
|
||||
* items for any such columns with null pointers. (We can't simply delete
|
||||
* them from the joinaliasvars list, because that would affect the attnums
|
||||
@@ -691,7 +691,7 @@ typedef struct XmlSerialize
|
||||
* decompiled queries.
|
||||
*
|
||||
* requiredPerms and checkAsUser specify run-time access permissions
|
||||
* checks to be performed at query startup. The user must have *all*
|
||||
* checks to be performed at query startup. The user must have *all*
|
||||
* of the permissions that are OR'd together in requiredPerms (zero
|
||||
* indicates no permissions checking). If checkAsUser is not zero,
|
||||
* then do the permissions checks using the access rights of that user,
|
||||
@@ -746,7 +746,7 @@ typedef struct RangeTblEntry
|
||||
* Fields valid for a join RTE (else NULL/zero):
|
||||
*
|
||||
* joinaliasvars is a list of (usually) Vars corresponding to the columns
|
||||
* of the join result. An alias Var referencing column K of the join
|
||||
* of the join result. An alias Var referencing column K of the join
|
||||
* result can be replaced by the K'th element of joinaliasvars --- but to
|
||||
* simplify the task of reverse-listing aliases correctly, we do not do
|
||||
* that until planning time. In detail: an element of joinaliasvars can
|
||||
@@ -843,9 +843,9 @@ typedef struct RangeTblFunction
|
||||
typedef struct WithCheckOption
|
||||
{
|
||||
NodeTag type;
|
||||
char *viewname; /* name of view that specified the WCO */
|
||||
Node *qual; /* constraint qual to check */
|
||||
bool cascaded; /* true = WITH CASCADED CHECK OPTION */
|
||||
char *viewname; /* name of view that specified the WCO */
|
||||
Node *qual; /* constraint qual to check */
|
||||
bool cascaded; /* true = WITH CASCADED CHECK OPTION */
|
||||
} WithCheckOption;
|
||||
|
||||
/*
|
||||
@@ -856,7 +856,7 @@ typedef struct WithCheckOption
|
||||
* You might think that ORDER BY is only interested in defining ordering,
|
||||
* and GROUP/DISTINCT are only interested in defining equality. However,
|
||||
* one way to implement grouping is to sort and then apply a "uniq"-like
|
||||
* filter. So it's also interesting to keep track of possible sort operators
|
||||
* filter. So it's also interesting to keep track of possible sort operators
|
||||
* for GROUP/DISTINCT, and in particular to try to sort for the grouping
|
||||
* in a way that will also yield a requested ORDER BY ordering. So we need
|
||||
* to be able to compare ORDER BY and GROUP/DISTINCT lists, which motivates
|
||||
@@ -876,15 +876,15 @@ typedef struct WithCheckOption
|
||||
* here, but it's cheap to get it along with the sortop, and requiring it
|
||||
* to be valid eases comparisons to grouping items.) Note that this isn't
|
||||
* actually enough information to determine an ordering: if the sortop is
|
||||
* collation-sensitive, a collation OID is needed too. We don't store the
|
||||
* collation-sensitive, a collation OID is needed too. We don't store the
|
||||
* collation in SortGroupClause because it's not available at the time the
|
||||
* parser builds the SortGroupClause; instead, consult the exposed collation
|
||||
* of the referenced targetlist expression to find out what it is.
|
||||
*
|
||||
* In a grouping item, eqop must be valid. If the eqop is a btree equality
|
||||
* In a grouping item, eqop must be valid. If the eqop is a btree equality
|
||||
* operator, then sortop should be set to a compatible ordering operator.
|
||||
* We prefer to set eqop/sortop/nulls_first to match any ORDER BY item that
|
||||
* the query presents for the same tlist item. If there is none, we just
|
||||
* the query presents for the same tlist item. If there is none, we just
|
||||
* use the default ordering op for the datatype.
|
||||
*
|
||||
* If the tlist item's type has a hash opclass but no btree opclass, then
|
||||
@@ -1140,7 +1140,7 @@ typedef struct SelectStmt
|
||||
* range table. Its setOperations field shows the tree of set operations,
|
||||
* with leaf SelectStmt nodes replaced by RangeTblRef nodes, and internal
|
||||
* nodes replaced by SetOperationStmt nodes. Information about the output
|
||||
* column types is added, too. (Note that the child nodes do not necessarily
|
||||
* column types is added, too. (Note that the child nodes do not necessarily
|
||||
* produce these types directly, but we've checked that their output types
|
||||
* can be coerced to the output column type.) Also, if it's not UNION ALL,
|
||||
* information about the types' sort/group semantics is provided in the form
|
||||
@@ -1446,7 +1446,7 @@ typedef struct AccessPriv
|
||||
*
|
||||
* Note: because of the parsing ambiguity with the GRANT <privileges>
|
||||
* statement, granted_roles is a list of AccessPriv; the execution code
|
||||
* should complain if any column lists appear. grantee_roles is a list
|
||||
* should complain if any column lists appear. grantee_roles is a list
|
||||
* of role names, as Value strings.
|
||||
* ----------------------
|
||||
*/
|
||||
@@ -1476,7 +1476,7 @@ typedef struct AlterDefaultPrivilegesStmt
|
||||
* Copy Statement
|
||||
*
|
||||
* We support "COPY relation FROM file", "COPY relation TO file", and
|
||||
* "COPY (query) TO file". In any given CopyStmt, exactly one of "relation"
|
||||
* "COPY (query) TO file". In any given CopyStmt, exactly one of "relation"
|
||||
* and "query" must be non-NULL.
|
||||
* ----------------------
|
||||
*/
|
||||
@@ -1575,7 +1575,7 @@ typedef struct CreateStmt
|
||||
*
|
||||
* If skip_validation is true then we skip checking that the existing rows
|
||||
* in the table satisfy the constraint, and just install the catalog entries
|
||||
* for the constraint. A new FK constraint is marked as valid iff
|
||||
* for the constraint. A new FK constraint is marked as valid iff
|
||||
* initially_valid is true. (Usually skip_validation and initially_valid
|
||||
* are inverses, but we can set both true if the table is known empty.)
|
||||
*
|
||||
@@ -1653,7 +1653,7 @@ typedef struct Constraint
|
||||
char fk_upd_action; /* ON UPDATE action */
|
||||
char fk_del_action; /* ON DELETE action */
|
||||
List *old_conpfeqop; /* pg_constraint.conpfeqop of my former self */
|
||||
Oid old_pktable_oid; /* pg_constraint.confrelid of my former self */
|
||||
Oid old_pktable_oid; /* pg_constraint.confrelid of my former self */
|
||||
|
||||
/* Fields used for constraints that allow a NOT VALID specification */
|
||||
bool skip_validation; /* skip validation of existing rows? */
|
||||
@@ -2094,7 +2094,7 @@ typedef struct SecLabelStmt
|
||||
* Declare Cursor Statement
|
||||
*
|
||||
* Note: the "query" field of DeclareCursorStmt is only used in the raw grammar
|
||||
* output. After parse analysis it's set to null, and the Query points to the
|
||||
* output. After parse analysis it's set to null, and the Query points to the
|
||||
* DeclareCursorStmt, not vice versa.
|
||||
* ----------------------
|
||||
*/
|
||||
@@ -2157,7 +2157,7 @@ typedef struct FetchStmt
|
||||
*
|
||||
* This represents creation of an index and/or an associated constraint.
|
||||
* If isconstraint is true, we should create a pg_constraint entry along
|
||||
* with the index. But if indexOid isn't InvalidOid, we are not creating an
|
||||
* with the index. But if indexOid isn't InvalidOid, we are not creating an
|
||||
* index, just a UNIQUE/PKEY constraint using an existing index. isconstraint
|
||||
* must always be true in this case, and the fields describing the index
|
||||
* properties are empty.
|
||||
@@ -2434,7 +2434,7 @@ typedef struct ViewStmt
|
||||
Node *query; /* the SELECT query */
|
||||
bool replace; /* replace an existing view? */
|
||||
List *options; /* options from WITH clause */
|
||||
ViewCheckOption withCheckOption; /* WITH CHECK OPTION */
|
||||
ViewCheckOption withCheckOption; /* WITH CHECK OPTION */
|
||||
} ViewStmt;
|
||||
|
||||
/* ----------------------
|
||||
@@ -2495,7 +2495,7 @@ typedef struct AlterSystemStmt
|
||||
{
|
||||
NodeTag type;
|
||||
VariableSetStmt *setstmt; /* SET subcommand */
|
||||
} AlterSystemStmt;
|
||||
} AlterSystemStmt;
|
||||
|
||||
/* ----------------------
|
||||
* Cluster Statement (support pbrown's cluster index implementation)
|
||||
|
||||
Reference in New Issue
Block a user