From 924954c670355f2a0ca1dd4173574a28fc0eedec Mon Sep 17 00:00:00 2001
From: Alexander Korotkov <akorotkov@postgresql.org>
Date: Sat, 27 Aug 2022 14:46:15 +0300
Subject: [PATCH] Fix typo in comment for writetuple() function

Reported-by: David Rowley
Discussion: https://postgr.es/m/CAApHDvrZ9Ky2LcWwcKsbdYChA850JE5qS%3DkGJiTNWS8mbBXZHw%40mail.gmail.com
---
 src/backend/utils/sort/tuplesort.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/backend/utils/sort/tuplesort.c b/src/backend/utils/sort/tuplesort.c
index d90a1aebdf..66950983e6 100644
--- a/src/backend/utils/sort/tuplesort.c
+++ b/src/backend/utils/sort/tuplesort.c
@@ -1340,7 +1340,7 @@ tuplesort_puttuple_common(Tuplesortstate *state, SortTuple *tuple, bool useAbbre
 }
 
 /*
- * Write a stored tuple onto tape.tuple.  Unless the slab allocator is
+ * Write a stored tuple onto tape.  Unless the slab allocator is
  * used, after writing the tuple, pfree() the out-of-line data (not the
  * SortTuple struct!), and increase state->availMem by the amount of
  * memory space thereby released.