Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ls70Q-0003Ls-5F for pgsql-hackers@arkaria.postgresql.org; Sat, 12 Jun 2021 17:01:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ls70M-0004s7-AA for pgsql-hackers@arkaria.postgresql.org; Sat, 12 Jun 2021 17:01:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ls70M-0004rw-2a for pgsql-hackers@lists.postgresql.org; Sat, 12 Jun 2021 17:01:06 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ls70K-0005fy-Bn for pgsql-hackers@lists.postgresql.org; Sat, 12 Jun 2021 17:01:05 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 15CH12lL2322000; Sat, 12 Jun 2021 13:01:02 -0400 From: Tom Lane To: Amit Kapila cc: Mark Dilger , PostgreSQL Hackers , Peter Eisentraut , Simon Riggs Subject: Re: logical replication of truncate command with trigger causes Assert In-reply-to: References: <1250962.1623192946@sss.pgh.pa.us> <1254157.1623196736@sss.pgh.pa.us> <1356183.1623250358@sss.pgh.pa.us> <1719083.1623351052@sss.pgh.pa.us> <1882577.1623425201@sss.pgh.pa.us> Comments: In-reply-to Amit Kapila message dated "Sat, 12 Jun 2021 12:45:28 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2321998.1623517262.1@sss.pgh.pa.us> Date: Sat, 12 Jun 2021 13:01:02 -0400 Message-ID: <2321999.1623517262@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Amit Kapila writes: > On Fri, Jun 11, 2021 at 8:56 PM Tom Lane wrote: >> I was thinking maybe we could mark all these replication protocol >> violation errors non-translatable. While we don't want to crash on a >> protocol violation, it shouldn't really be a user-facing case either. > I don't see any problem with that as these are not directly related to > any user operation. So, +1 for making these non-translatable. Done that way. On re-reading the code, there were a bunch more Asserts that could be triggered by bad input data, so the committed patch has rather more corrections than I posted before. regards, tom lane