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

diff --git a/src/backend/executor/nodeIncrementalSort.c b/src/backend/executor/nodeIncrementalSort.c
index e056469448c3b1e3a757c08bd979f7f3837c2637..6c0d24ee25a5b9c2b6be988d8b0fd2907a6272f6 100644 (file)
--- 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