diff options
| author | Amit Kapila <akapila@postgresql.org> | 2020-07-20 07:54:04 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2020-07-20 07:54:04 +0530 |
| commit | 4a1ae21750cbf23d8317d565c55ac7bce46bf0f6 (patch) | |
| tree | 38c9e7e8049c883cc340c00cd8da1cd8067d6cf5 | |
| parent | 914d2383ae91918b359311a90d23c0d5862781ac (diff) | |
| download | postgresql-4a1ae21750cbf23d8317d565c55ac7bce46bf0f6.tar.gz postgresql-4a1ae21750cbf23d8317d565c55ac7bce46bf0f6.zip | |
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
| -rw-r--r-- | src/backend/executor/nodeIncrementalSort.c | 4 |
1 files 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 |