Subject: [PATCH 5/9] document store_change somewhat more

From: Álvaro Herrera <[email-masked]>
Date: Thu, 12 Mar 2026 16:10:47 +0100

---
 .../replication/pgoutput_repack/pgoutput_repack.c        | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/src/backend/replication/pgoutput_repack/pgoutput_repack.c b/src/backend/replication/pgoutput_repack/pgoutput_repack.c
index 90f3a8975b9..79fc611b9ff 100644
--- a/src/backend/replication/pgoutput_repack/pgoutput_repack.c
+++ b/src/backend/replication/pgoutput_repack/pgoutput_repack.c
@@ -158,7 +158,14 @@ plugin_change(LogicalDecodingContext *ctx, ReorderBufferTXN *txn,
 	}
 }
 
-/* Store concurrent data change. */
+/*
+ * For each change affecting the table being repacked, we store enough
+ * information about each tuple in it, so that it can be replayed in the
+ * new copy of the table.
+ *
+ * XXX for DELETE and the UPDATE OLD tuples, we could store just the
+ * replication identity instead of the full tuple.
+ */
 static void
 store_change(LogicalDecodingContext *ctx, Relation relation,
 			 ConcurrentChangeKind kind, HeapTuple tuple)
-- 
2.47.3

--pnppmxqkefjd4hu2
Content-Type: text/plain; charset=utf-8
Content-Disposition: attachment;
	filename*0="0006-use-int-instead-of-uint32-for-the-result-of-list_len.noc";
	filename*1="fbot.txt"