Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vhgcy-004B6j-0x for pgsql-hackers@arkaria.postgresql.org; Mon, 19 Jan 2026 04:12:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vhgcw-00BRhb-0z for pgsql-hackers@arkaria.postgresql.org; Mon, 19 Jan 2026 04:12:30 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vhgcv-00BRhT-38 for pgsql-hackers@lists.postgresql.org; Mon, 19 Jan 2026 04:12:30 +0000 Received: from mail-qt1-x836.google.com ([2607:f8b0:4864:20::836]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vhgcu-001GnZ-06 for pgsql-hackers@lists.postgresql.org; Mon, 19 Jan 2026 04:12:30 +0000 Received: by mail-qt1-x836.google.com with SMTP id d75a77b69052e-502a2370e4fso23279291cf.3 for ; Sun, 18 Jan 2026 20:12:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1768795946; x=1769400746; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=jF1MHRD9SBzQ2lBzFxlMpbG79v6LaY6QuMLji+OAaEs=; b=IKvd+fLSsxOutbm9dz91DQfvij19wPYFfM0ZUYqtETQ97T1XXHxxBUW0LlEAprAAtf ojFacTD1GXEdexBw6CLfKAG5GcwjnqVNAZ/rdw3qbN06nOzEaEH2DVzm17rIjx39r8PY JZyz7VpvHcCMfSMgCtEaVj6JSvin2WrFH26/NaA5Y6IA+HBV4UEbqV+NZJAh62cghFjo KpdLnYNCOEnwwv6gdh3rfzHFWRNbKC3LY/13Yjs9FuEP8trjqqx2zFE1ONCM/JpNdsy3 pnu7Y8Q9VGVZdYGgriZ7b5LDLUp6shYQGK8s5wwP80HKkII4zQtZk7BtwlCne9dcsIsR hYmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768795946; x=1769400746; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=jF1MHRD9SBzQ2lBzFxlMpbG79v6LaY6QuMLji+OAaEs=; b=NCm8RHUXDEnD/Z0wRM9KTnIpZd+LoFQSLdeHmYQIyPe+cxaskIjujT0A8Zo1YMgWWR 1da/jE3kwPy7u314wFrwgJt2Z/SPJH9V5TnL4m519AXWsCBC0+7yMQEyxth+mBfxXTIP D1sqr4mZ2C6VLXxKcQzE7N0qITG1lI2/iNgJhtdQVJlHLofmbMLrp42Gi6PaUL7Lj6JB jYK4aGy7GZi+ausimuE919kCroDtpc43goIGFDDdl6kbFcQMnrf4TD2r1fTBbprySnB8 HeeuB6BbXjHRt/Lt4Zm7jdjqW2YCB6pPaCV3q6Kjn/uXJUjkh63efol1TzCFrWnmzTqV NUAQ== X-Forwarded-Encrypted: i=1; AJvYcCVHjOQLhurhlJL5N0i/CzVkNnDaOV+m/MGCV/A2+a8SZ/v143kszRKOgSgaLwoXGQdA3bjqbF8B9AfRV9dH@lists.postgresql.org X-Gm-Message-State: AOJu0YwntyYAfgwLww/PPY/BVoDVl2wRa2i/WW1cAcDYG1fMqkKkWHAO n6RYmNY7aQMya08tMiqh+WIst2JdQy3/NIhkYVIqtTCcUDB/hIr8E1l9a/Q39dzKwour6jUtAHP 4GTzsa2g+J8lXJOrNHxqWpISVuACWeOc= X-Gm-Gg: AY/fxX57ByvGU46e/uPbLkGD8rOH4L4Pb1khjO2JOsJkVwregUat0BMEhSHHltJSf2c gEbfVyzl+FMAqs2Udefbc1F1J8V+SbZiE8lbjOB5TZKetulwrDMvuoQjfaXr9dxJL0EDLXx3Nmf 1jerNhp4BVONxcYqFKUIf+Y+aDAgH7Ge/7K1yWiJDx3x8XquSEo4VX+cPGMJykQ9leBE0vQ6nez Tl/GpsuJq0nc2vb2qmXTG/Q3E+k2Xf6OEoIyxlPVfAbhQR17F+UEQItEDnr9iVcu13eGjt1AX4M +M4NeSWBUZU1mIIvsN9W90p9U4TMuA== X-Received: by 2002:ac8:5ac2:0:b0:4ed:aeaa:ec4d with SMTP id d75a77b69052e-502a17d247emr161133331cf.77.1768795945980; Sun, 18 Jan 2026 20:12:25 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Peter Smith Date: Mon, 19 Jan 2026 15:11:59 +1100 X-Gm-Features: AZwV_Qgb9lBQiNnRlD6GPOuI9xPkSg2aci4UYN5DGlgCl3cHsEddn3cFJKW4OIg Message-ID: Subject: Re: Proposal: Conflict log history table for Logical Replication To: Dilip Kumar Cc: Amit Kapila , shveta malik , vignesh C , Masahiko Sawada , Bharath Rupireddy , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Some review comments for v22-0003. ====== 1. It looks like none of my previous v20-0003 review comments [1] have been addressed. Maybe accidentally overlooked? ====== 2. + + + The internal conflict logging table is strictly tied to the lifecycle of the + subscription or the conflict_log_destination setting. If + the subscription is dropped, or if the destination is changed to + log, the table and all its recorded conflict data are + permanently deleted. To perform a post-mortem analysis + after removing a subscription, users must manually back up or rename the + conflict table before the deletion occurs. + + 2a. Let's consistently call this the "Conflict log table", same as everywhere else, not "logging table". ~ 2b. This is only a caution for the CLT, so I felt it's better to put this in the scope of the 'table' param value. ~~~ 3. + analysis of conflicts. This table is automatically dropped when the + subscription is removed. If you move the to this scope, as suggested above in #2b, then you can remove the sentence "This table is automatically dropped when the subscription is removed", because that is duplicate information you already wrote in the caution. ====== [1] v20 docs review - https://www.postgresql.org/message-id/CAHut%2BPuzB4gNYvqX9hb28KE0RK_xhU%2B2-%3DwUfL5OEVUCi92Hqw%40mail.gmail.com Kind Regards, Peter Smith. Fujitsu Australia