From 022061464ac99ee9c0b38f77eb47b7afdef481c4 Mon Sep 17 00:00:00 2001 From: "Chao Li (Evan)" Date: Thu, 16 Apr 2026 11:18:26 +0800 Subject: [PATCH v2] repack: clarify final phase of concurrent mode in file header comment Author: Chao Li Reviewed-by: Jakub Wartak Discussion: https://postgr.es/m/06F150E0-FDE9-4FC6-9EEF-79A759430471@gmail.com --- src/backend/commands/repack.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/backend/commands/repack.c b/src/backend/commands/repack.c index ec100e3eef5..5b18ac9c581 100644 --- a/src/backend/commands/repack.c +++ b/src/backend/commands/repack.c @@ -17,9 +17,10 @@ * from being reserved), and accumulates the changes in a file. Once the * initial copy is complete, we read the changes from the file and re-apply * them on the new heap. Then we upgrade our ShareUpdateExclusiveLock to - * AccessExclusiveLock and swap the relfilenodes. This way, the time we hold - * a strong lock on the table is much reduced, and the bloat is eliminated. - * + * AccessExclusiveLock, decode and apply any remaining changes that occurred + * during the first re-apply pass, and swap the relfilenodes. This way, the + * time we hold a strong lock on the table is much reduced, and the bloat + * is eliminated. * * Portions Copyright (c) 1996-2026, PostgreSQL Global Development Group * Portions Copyright (c) 1994-5, Regents of the University of California -- 2.50.1 (Apple Git-155)