mirror of
https://github.com/postgres/postgres.git
synced 2025-06-17 17:02: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:
@ -437,7 +437,7 @@ check_agg_arguments(ParseState *pstate,
|
||||
|
||||
/*
|
||||
* Now check for vars/aggs in the direct arguments, and throw error if
|
||||
* needed. Note that we allow a Var of the agg's semantic level, but not
|
||||
* needed. Note that we allow a Var of the agg's semantic level, but not
|
||||
* an Agg of that level. In principle such Aggs could probably be
|
||||
* supported, but it would create an ordering dependency among the
|
||||
* aggregates at execution time. Since the case appears neither to be
|
||||
@ -815,7 +815,7 @@ parseCheckAggregates(ParseState *pstate, Query *qry)
|
||||
/*
|
||||
* If there are join alias vars involved, we have to flatten them to the
|
||||
* underlying vars, so that aliased and unaliased vars will be correctly
|
||||
* taken as equal. We can skip the expense of doing this if no rangetable
|
||||
* taken as equal. We can skip the expense of doing this if no rangetable
|
||||
* entries are RTE_JOIN kind. We use the planner's flatten_join_alias_vars
|
||||
* routine to do the flattening; it wants a PlannerInfo root node, which
|
||||
* fortunately can be mostly dummy.
|
||||
@ -853,7 +853,7 @@ parseCheckAggregates(ParseState *pstate, Query *qry)
|
||||
*
|
||||
* Note: because we check resjunk tlist elements as well as regular ones,
|
||||
* this will also find ungrouped variables that came from ORDER BY and
|
||||
* WINDOW clauses. For that matter, it's also going to examine the
|
||||
* WINDOW clauses. For that matter, it's also going to examine the
|
||||
* grouping expressions themselves --- but they'll all pass the test ...
|
||||
*/
|
||||
clause = (Node *) qry->targetList;
|
||||
@ -984,7 +984,7 @@ check_ungrouped_columns_walker(Node *node,
|
||||
/*
|
||||
* If we have an ungrouped Var of the original query level, we have a
|
||||
* failure. Vars below the original query level are not a problem, and
|
||||
* neither are Vars from above it. (If such Vars are ungrouped as far as
|
||||
* neither are Vars from above it. (If such Vars are ungrouped as far as
|
||||
* their own query level is concerned, that's someone else's problem...)
|
||||
*/
|
||||
if (IsA(node, Var))
|
||||
@ -1015,7 +1015,7 @@ check_ungrouped_columns_walker(Node *node,
|
||||
|
||||
/*
|
||||
* Check whether the Var is known functionally dependent on the GROUP
|
||||
* BY columns. If so, we can allow the Var to be used, because the
|
||||
* BY columns. If so, we can allow the Var to be used, because the
|
||||
* grouping is really a no-op for this table. However, this deduction
|
||||
* depends on one or more constraints of the table, so we have to add
|
||||
* those constraints to the query's constraintDeps list, because it's
|
||||
|
Reference in New Issue
Block a user