postgres.git / summary / log / commit / refs

commit    044dc7b964147ec6303d59320fb743693b22af30
Author:   Amit Kapila <akapila@postgresql.org>
Date:     Mon Jul 20 02:15:26 2020 +0000
First released in: 14.0, 13.0

    Fix minor typo in nodeIncrementalSort.c.
    
    Author: Vignesh C
    Reviewed-by: James Coleman
    Backpatch-through: 13, where it was introduced
    Discussion: https://postgr.es/m/CALDaNm0WjZqRvdeL59ZfYH0o4mLbKQ23jm-bnjXcFzgpANx55g@mail.gmail.com


 src/backend/executor/nodeIncrementalSort.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/backend/executor/nodeIncrementalSort.c b/src/backend/executor/nodeIncrementalSort.c
index e056469448c..6c0d24ee25a 100644
--- a/src/backend/executor/nodeIncrementalSort.c
+++ b/src/backend/executor/nodeIncrementalSort.c
@@ -65,8 +65,8 @@
  *	into the second mode if we believe it's beneficial.
  *
  *	Sorting incrementally can potentially use less memory, avoid fetching
- *	and sorting all tuples in the the dataset, and begin returning tuples
- *	before the entire result set is available.
+ *	and sorting all tuples in the dataset, and begin returning tuples before
+ *	the entire result set is available.
  *
  *	The hybrid mode approach allows us to optimize for both very small
  *	groups (where the overhead of a new tuplesort is high) and very	large


[parent: a766d6ca22ac]