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 1lrj3Y-0004ez-4v for pgsql-hackers@arkaria.postgresql.org; Fri, 11 Jun 2021 15:26:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lrj3X-00071I-3l for pgsql-hackers@arkaria.postgresql.org; Fri, 11 Jun 2021 15:26:47 +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 1lrj3W-000719-SS for pgsql-hackers@lists.postgresql.org; Fri, 11 Jun 2021 15:26:46 +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 1lrj3U-0002RK-Mp for pgsql-hackers@lists.postgresql.org; Fri, 11 Jun 2021 15:26:45 +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 15BFQfBC1882578; Fri, 11 Jun 2021 11:26:41 -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> Comments: In-reply-to Amit Kapila message dated "Fri, 11 Jun 2021 10:59:53 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1882576.1623425201.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 11 Jun 2021 11:26:41 -0400 Message-ID: <1882577.1623425201@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 12:20 AM Tom Lane wrote: >> Another thing >> I'm wondering is how many of these messages really need to be >> translated. We could use errmsg_internal and avoid burdening the >> translators, perhaps. > Not sure but I see all existing similar ereport calls don't use errmsg_i= nternal. 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. Thoughts? regards, tom lane