From 569b7769aa56b4edb992965e8bd02ff3d20635fe Mon Sep 17 00:00:00 2001
From: root <root@localhost.localdomain>
Date: Thu, 14 Jan 2021 23:54:17 -0500
Subject: [PATCH] fix typo

---
 src/backend/replication/logical/reorderbuffer.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/backend/replication/logical/reorderbuffer.c b/src/backend/replication/logical/reorderbuffer.c
index 5a62ab8..036c36f 100644
--- a/src/backend/replication/logical/reorderbuffer.c
+++ b/src/backend/replication/logical/reorderbuffer.c
@@ -4737,7 +4737,7 @@ ReorderBufferToastReset(ReorderBuffer *rb, ReorderBufferTXN *txn)
  * always rely on stored cmin/cmax values because of two scenarios:
  *
  * * A tuple got changed multiple times during a single transaction and thus
- *	 has got a combocid. Combocid's are only valid for the duration of a
+ *	 has got a combocid. Combocids are only valid for the duration of a
  *	 single transaction.
  * * A tuple with a cmin but no cmax (and thus no combocid) got
  *	 deleted/updated in another transaction than the one which created it
-- 
1.8.3.1

