Re: logical replication of truncate command with trigger causes Assert - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: logical replication of truncate command with trigger causes Assert
Date
Msg-id 202106121843.c4uagunajhpm@alvherre.pgsql
Whole thread Raw
In response to Re: logical replication of truncate command with trigger causes Assert  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2021-Jun-12, Tom Lane wrote:

> Amit Kapila <amit.kapila16@gmail.com> writes:
> > On Fri, Jun 11, 2021 at 8:56 PM Tom Lane <tgl@sss.pgh.pa.us> 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.

Good call, thanks.  Not only it's not very useful to translate such
messages, but it's also quite a burden because some of them are
difficult to translate.

-- 
Álvaro Herrera       Valdivia, Chile
"Tiene valor aquel que admite que es un cobarde" (Fernandel)



pgsql-hackers by date:

Previous
From: Yugo NAGATA
Date:
Subject: Re: Error on pgbench logs
Next
From: Yugo NAGATA
Date:
Subject: Avoid stuck of pbgench due to skipped transactions