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 1vfbeB-003JWm-2V for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Jan 2026 10:29:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vfbeA-004CW4-3B for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Jan 2026 10:29:11 +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 1vfbeA-004CVv-21 for pgsql-hackers@lists.postgresql.org; Tue, 13 Jan 2026 10:29:10 +0000 Received: from mail-pl1-x632.google.com ([2607:f8b0:4864:20::632]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vfbe8-000CLF-32 for pgsql-hackers@lists.postgresql.org; Tue, 13 Jan 2026 10:29:10 +0000 Received: by mail-pl1-x632.google.com with SMTP id d9443c01a7336-2a3e89aa5d0so57495125ad.1 for ; Tue, 13 Jan 2026 02:29:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1768300147; x=1768904947; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=xvXKhpVmgX0rDjad2WEeirFZpoEP96YxM2BvIhZKOQY=; b=PuU76uU1WPgmAkozhqS9IzLKq4nK3ZwAeQUbF3BXwaqGSH5KsMQt3/fWoHVXTPhmZ/ wTC4XDY+/y6L931JK9mtZv9W/z0IOns1k7JEjU9KSECmnqedtxxGKkDI4Wvv0V5CUwf6 XTPEEdC4e219JI4qy/pIGl0K00HJyg71dUo/enhBMgIBfYSZ7TGlJCcuQoQpLzpG0qeH 9N/YiLS1L8ivYvNwbD2CmJov6ugOAwgGR9CeiyWyNiTfTS/rsZMPiWSYL+2qQqKt/Un3 H0vmJnD64IOgBSUXuXSyQiX0hjJditK+/w94Ld3oEGfnAoufOdBiyqWg8SE3aO9zGnoe vKzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768300147; x=1768904947; h=content-transfer-encoding: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=xvXKhpVmgX0rDjad2WEeirFZpoEP96YxM2BvIhZKOQY=; b=uvBeEN+hVdRHiP9Rwz/gaRU0DyuJHisw0f1xXbBFleLTLQ0iu9I511MkuWVtnrc/bI pLK8T6De+5v6Lv/Cr5ESk+Hkn3DeYz54fb+93lZCjIa9DSfidE7gFBjQB87X5nzF7xDv iavxkm3jtdyxSbykZsnhQf9/2luDHdHbITQFEKqiF8O8U07L8QtGUrAB3MLYa4NqV6V1 WCSNZ1gHS0M/yVD01h/XxGXz0lCp3Y7o3LQ6HNNWs7EgMi8dkgxsEOp15d3etNSvueG6 b53sKXDYwZSilKnzt04rY3gmFcvbsHQaqWA1U4h02zfJl5/BALKzWx76M4REPqCIBA4B 42KA== X-Forwarded-Encrypted: i=1; AJvYcCUbYOjvOoZSbrculdupu5pl3vIqKk1yHps79svTNe0FOQ040XVzQvSuLQLHtr7qJhRsrlb6NGCUFbDMjUYb@lists.postgresql.org X-Gm-Message-State: AOJu0YwbguFJo+wX3pQ4+pyUNjs/F4D8Cr7/JJOsFmCcwzGf+Y8uehLA GDDHPufmENKeo+v+3SIScMsiUyeB97PbKWcw+M7frD5/FdyqIVfsFp25CvVXd8/hItX7HFpl76y 8Xx/3s+XL3T82ECBOqxEVKz73Akp8IJQ= X-Gm-Gg: AY/fxX6OOEvHz8CSyCX8VNjLWp9oQvmXtFANJXYvq4uFY+kilBozFWaaJAEJ7Vmt4VA is9mUzY6fHKkS9fz0QImrApHoXKv+bv76BN2BCIt5XWBH6HQCZPH59bzT4oNJk3857v3ORqvDJF YzOcqDMCZyzx1xQCFukda/nM3XfUO5GS5N6qDjZuAwTbbqlbwoUtzwMnp1FewacoHcXYFDzjgND AGts0oYfdJ9OORmdRMx9BaMwFcuVju7gJyY2ACeHtrKEmhoTX70fdLx3s9htnZ82XhLQZN8ESyF UafMKqmccqpzfH3AOzpDPt7UMPCv+hDiH8ItRls4AkiRFxUbnGd2snTgxutSfUp+KP3v0hAW X-Google-Smtp-Source: AGHT+IEqrOE9p1XQJoIVZOzoPh5h27VLGX+GIHK5FHDmVeHcQQkDbUv088UlEEcvNHJgomgp5E6o+KoYkvlrlEZMhmY= X-Received: by 2002:a17:902:d50d:b0:2a0:bea0:8207 with SMTP id d9443c01a7336-2a3ee49e052mr201891445ad.49.1768300146883; Tue, 13 Jan 2026 02:29:06 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: shveta malik Date: Tue, 13 Jan 2026 15:58:54 +0530 X-Gm-Features: AZwV_QhFOFuJfHLXrhMtnKj4WLVhQvv7Nj79-ezsiyjwYTpd34jGQe3GLmHNFoM Message-ID: Subject: Re: Proposal: Conflict log history table for Logical Replication To: Dilip Kumar Cc: Peter Smith , vignesh C , Amit Kapila , Masahiko Sawada , Bharath Rupireddy , PostgreSQL Hackers , shveta malik Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, Jan 10, 2026 at 6:45=E2=80=AFPM Dilip Kumar = wrote: > >> > Here is the updated patch > Thanks, I will review the code. Few concerns while experimenting with 001 a= lone: 1) I am able to insert and update rows in pg_conflict.pg_conflict_16394. It should be restricted. 2) I think we need to block 'SELECT for UPDATE' and similar operations on CLT. Currently it is allowed on CLT. See this: postgres=3D# SELECT * FROM pg_toast.pg_toast_3466 for UPDATE; ERROR: cannot lock rows in TOAST relation "pg_toast_3466" postgres=3D# SELECT * FROM pg_conflict.pg_conflict_16394 for UPDATE; .... (1 row) 3) We currently skip ANALYZE on TOAST tables, but I=E2=80=99m not sure whether the same restriction should apply to CLT. Since users are expected to query CLT frequently, collecting statistics could be beneficial. Even though there are currently no indexes or other structures to enable more optimal plans, having statistics should not harm. Thoughts? postgres=3D# analyze pg_toast.pg_toast_16399; WARNING: skipping "pg_toast_16399" --- cannot analyze non-tables or special system tables postgres=3D# analyze pg_conflict.pg_conflict_16394; ANALYZE 4) It will be good to show 'Conflict Log Table:' in \dRs command. thanks Shveta