aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2016-10-04 09:46:43 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2016-10-04 09:47:54 +0300
commitc86c2d9d57c1e6c5fec860873734cccaf31df5b0 (patch)
treeaccddefeb378f172f20a53a00d58f4109b2980ac /src
parent61633f79048d040aefeed68dcac0e0b996a06189 (diff)
downloadpostgresql-c86c2d9d57c1e6c5fec860873734cccaf31df5b0.tar.gz
postgresql-c86c2d9d57c1e6c5fec860873734cccaf31df5b0.zip
Update comment.
mergepreread()/mergeprereadone() don't exist anymore, the function that does roughly the same is now called mergereadnext().
Diffstat (limited to 'src')
-rw-r--r--src/backend/utils/sort/tuplesort.c16
1 files changed, 8 insertions, 8 deletions
diff --git a/src/backend/utils/sort/tuplesort.c b/src/backend/utils/sort/tuplesort.c
index 20cfb0b139c..5ff81ed95aa 100644
--- a/src/backend/utils/sort/tuplesort.c
+++ b/src/backend/utils/sort/tuplesort.c
@@ -3083,14 +3083,14 @@ dumpbatch(Tuplesortstate *state, bool alltuples)
* a call with no subsequent run actually written to destTape), we prefer
* to write out a 0 tuple run.
*
- * mergepreread()/mergeprereadone() are prepared for 0 tuple runs, and
- * will reliably mark the tape inactive for the merge when called from
- * beginmerge(). This case is therefore similar to the case where
- * mergeonerun() finds a dummy run for the tape, and so doesn't need to
- * merge a run from the tape (or conceptually "merges" the dummy run, if
- * you prefer). According to Knuth, Algorithm D "isn't strictly optimal"
- * in its method of distribution and dummy run assignment; this edge case
- * seems very unlikely to make that appreciably worse.
+ * mergereadnext() is prepared for 0 tuple runs, and will reliably mark
+ * the tape inactive for the merge when called from beginmerge(). This
+ * case is therefore similar to the case where mergeonerun() finds a dummy
+ * run for the tape, and so doesn't need to merge a run from the tape (or
+ * conceptually "merges" the dummy run, if you prefer). According to
+ * Knuth, Algorithm D "isn't strictly optimal" in its method of
+ * distribution and dummy run assignment; this edge case seems very
+ * unlikely to make that appreciably worse.
*/
Assert(state->status == TSS_BUILDRUNS);