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 1vi98M-00GMzs-1M for pgsql-hackers@arkaria.postgresql.org; Tue, 20 Jan 2026 10:38:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vi98L-000QEu-1V for pgsql-hackers@arkaria.postgresql.org; Tue, 20 Jan 2026 10:38:49 +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 1vi98L-000QEm-0O for pgsql-hackers@lists.postgresql.org; Tue, 20 Jan 2026 10:38:49 +0000 Received: from mail-pg1-x529.google.com ([2607:f8b0:4864:20::529]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vi98J-001VOo-1Y for pgsql-hackers@lists.postgresql.org; Tue, 20 Jan 2026 10:38:49 +0000 Received: by mail-pg1-x529.google.com with SMTP id 41be03b00d2f7-b98983bae80so2075214a12.0 for ; Tue, 20 Jan 2026 02:38:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1768905525; cv=none; d=google.com; s=arc-20240605; b=bfszBlnoWXa3RNAD8OH/4ymxd43qhWfeCzAmonjslCfMI1CAc+/YUHwpusptsH0Tgo wCEyEgQfCBQ6oGRKdRO+NY3iGGQ43Ae/iW/hiobWgcVwaY7k0+Nt3mlTF4A7dLDgm/Vz FKoVWo1Flj6Nhohmee61j06Kp0igdp7anO1lApUOt1VkKz0DInTNhOzpn0D+MdZFZnOy M2RDX+79lkiKUqD+cHWoNCRCP8KZnlITRCSfbUUeEY7PWT85L2M4xhdw0XaoOC8JzMJA X4b7rV84/Z6hrv/QRo89jLp0VcyedBjviI3/RKG9NOoygaXbqOQWJgZM/Ru0XoO2kt23 awlw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=M2L56Ex9k1Jss9yenHzzLM9FOBwOhhDB+hrZy7Z/jvM=; fh=JjP+QfssMNywGmeBLNHZqLJxW3CGPJ99bAfmt46LUwA=; b=OQhhhOlcn4PuXZAh8o2WVaqMmLY1Q3XWz84rgr95FK/8oibvbP2IzuPrDTq+HYUL1P cic8yv7y27VQs7j55fiwX7CyuQZBK/3IKlcFCFPImbu9Tr03ovbDw5i+9Pcg8ldoC2Cz i2ZQgezS+cPRwzVmL+uIa8zqrN0clyWCg3+c/InunScfkt+P++DA60GIFd+X3SCujw0Z 1AkMJPePhXwt60WIec0CVZkd+5YFVCzb+Ds2SaUDoPrib4npqJcPpUXB+WHYZkPfmpBJ eho3VlG5++4YtL3iEAacdZxmMumFBUVD2zpT7Zrx5PH584ZLxqFT4Uy9Bz4kGV6ANCUF jstQ==; darn=lists.postgresql.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1768905525; x=1769510325; 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=M2L56Ex9k1Jss9yenHzzLM9FOBwOhhDB+hrZy7Z/jvM=; b=PpvUTjLs50UT6/safWFdCGEk5Ub8KoVvbs32cLSAljc/xYxLMLOOjdEOnVYqHbERFk JiMYuNN1Kl9a02nEzULt0fFrcP22nSrAJp0yhUqqyIJQnuawStNEuEyU009SBFfK3vv9 h1bU+/XvfTmThxHjktNGwS3X7oqYePtdpKMaXDSssCcaQzJR/Mz7eOUMQaT1dGtimewz XELHFIPnFsZ5lHTvORHlmyIAzupcoaGOJzdFufoVnxrZ/MfAtRFJxoPmMMCk8V866MIu tcctjM4X99qFK2pG0/9KCUEk3dn2D0RvuXS0c+T6yLRieYRc5wJ2mWjHS6eyfPpG9pha lHjw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768905525; x=1769510325; 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=M2L56Ex9k1Jss9yenHzzLM9FOBwOhhDB+hrZy7Z/jvM=; b=OmGY8yq1uyvMakqPPuHRszTi8Q0wZ/ikI5hzlvthAxhvjE9tptMRCq/LREoXkOW3AT JyPxd90aIShV/x0VZFRlgYC2Sg7885HG8rDXcHmNF6I5FmurHxXuk5Ugglalfr2GjHX5 UQBip/+1eyk0h/Iff6osuKFqQXAyW0/6UoJou3w5iXxy1xmjzaVlnla5JgUJk36kYxcD tzh+TWkVB2/VxBMxDJSrQ9GgmjVrJZo/ji7HPj3ge6bcZcFmy/KTjSUyEennJxlgnW7A ZmeSwCoIC4LyzSpqVXz1FRuHCCNZNr4hGgAQU6bkJgun0Cqjj832vL99jk3eCzYRwoUb b2bQ== X-Forwarded-Encrypted: i=1; AJvYcCWrse0TIZir8Mie/3rkLtmdd173FmSoKdEH1R/V+HLujLtLowJt4IddqlasfdHzIQ+yzdsbqEQKtuk3AZ0X@lists.postgresql.org X-Gm-Message-State: AOJu0Yy0POfdkyq6ZgpzVVQI1PyvgGCV7OyyilN5wybQrqaHU6V34/gq ElF3vCAurHZzraD0YeUnZGo/USJN7I9AS6Ci3vvRJxAWYOy/vJuxEvxKeQ7vsSyMdmi6oYCt0Fv WQRGRWbKogvhz3m4BEUJAn+O05ikAxao= X-Gm-Gg: AZuq6aKvhRZmxBPsw9WTK7ZUeSxE6+lcr0ZxWozdGYpcKxh07m6Mv7wP+dMGsLiDtox x/ymfu3FXiFKhM8jtU1UE54LZLjgq+yc5OmUm928ih9OcMWWLbuatiqCsLPlRicDkGkc3KIAUfT qeCV5KdtApIWJDvd6M8Mot93QpcsUO452PLa1B0PIm9+Y2+iBhypCPa42DbKc9wSPtaEmYR9T64 Rx6rNehsSXsydOAyBLL4ij8S3V1RBRoB7J+PLbaswB/51VlohLyx2Ie3yFcWiS2Dnu2iFzZkhJs /4W0UJ+TP3Z7WsSDLFMaE0qO9YS58lOv+frAz3Yzug== X-Received: by 2002:a17:90b:58ed:b0:340:bfcd:6af8 with SMTP id 98e67ed59e1d1-3527313bf59mr9283344a91.4.1768905525086; Tue, 20 Jan 2026 02:38:45 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: shveta malik Date: Tue, 20 Jan 2026 16:08:33 +0530 X-Gm-Features: AZwV_Qj5Ix9LcPNiEbMRyZHPiGnXZuThcrtyCGBGpBQ2zSo5NZY8MKl8YryevRo 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 Tue, Jan 13, 2026 at 4:09=E2=80=AFPM Dilip Kumar = wrote: > > On Tue, Jan 13, 2026 at 3:59=E2=80=AFPM shveta malik wrote: > > > > 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; > > .... > I had a quick look at v23-001, I see that it has INSERT and UPDATE blocked but SELECt for UPDATE is still working. I do not see any strong need to provide this flexibility for user-level concurrency control on conflict-tables. Shall this be blocked as well? Also, the error I get for INSERT and UPDATE is: postgres=3D# update pg_conflict.pg_conflict_16390 set relid=3D1; ERROR: cannot modify or insert data for conflict log table "pg_conflict_16= 390" DETAIL: Conflict log tables are system-managed and only support cleanup via DELETE or TRUNCATE. I feel "cannot modify or insert data into conflict log table ..." seems more natural. thanks Shveta