mirror of
https://github.com/postgres/postgres.git
synced 2025-07-09 22:41:56 +03:00
Fix some grammar and typos in comments and docs
The documentation fixes are backpatched down to where they apply. Author: Justin Pryzby Discussion: https://postgr.es/m/20201031020801.GD3080@telsasoft.com Backpatch-through: 9.6
This commit is contained in:
@ -3266,7 +3266,7 @@ ExecBuildAggTransCall(ExprState *state, AggState *aggstate,
|
||||
*
|
||||
* For ordered aggregates:
|
||||
*
|
||||
* Only need to choose between the faster path for a single orderred
|
||||
* Only need to choose between the faster path for a single ordered
|
||||
* column, and the one between multiple columns. Checking strictness etc
|
||||
* is done when finalizing the aggregate. See
|
||||
* process_ordered_aggregate_{single, multi} and
|
||||
|
@ -1097,7 +1097,7 @@ ExecEndIncrementalSort(IncrementalSortState *node)
|
||||
ExecClearTuple(node->ss.ss_ScanTupleSlot);
|
||||
/* must drop pointer to sort result tuple */
|
||||
ExecClearTuple(node->ss.ps.ps_ResultTupleSlot);
|
||||
/* must drop stanalone tuple slots from outer node */
|
||||
/* must drop standalone tuple slots from outer node */
|
||||
ExecDropSingleTupleTableSlot(node->group_pivot);
|
||||
ExecDropSingleTupleTableSlot(node->transfer_tuple);
|
||||
|
||||
|
@ -105,7 +105,7 @@ ExecLimit(PlanState *pstate)
|
||||
}
|
||||
|
||||
/*
|
||||
* Tuple at limit is needed for comparation in subsequent
|
||||
* Tuple at limit is needed for comparison in subsequent
|
||||
* execution to detect ties.
|
||||
*/
|
||||
if (node->limitOption == LIMIT_OPTION_WITH_TIES &&
|
||||
|
Reference in New Issue
Block a user