Re: Error code for checksum failure in origin.c - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Error code for checksum failure in origin.c
Date
Msg-id CAA4eK1JS_fDvrTRJuFy7wQADZaKmaNGFC3na4wXQUWhfHhyj=w@mail.gmail.com
Whole thread Raw
In response to Re: Error code for checksum failure in origin.c  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Error code for checksum failure in origin.c  (Michael Paquier <michael@paquier.xyz>)
Re: Error code for checksum failure in origin.c  (Kasahara Tatsuhito <kasahara.tatsuhito@gmail.com>)
Re: Error code for checksum failure in origin.c  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
On Thu, Aug 26, 2021 at 4:11 PM Daniel Gustafsson <daniel@yesql.se> wrote:
>
> > On 26 Aug 2021, at 12:03, Amit Kapila <amit.kapila16@gmail.com> wrote:
> >
> > On Thu, Aug 26, 2021 at 3:18 PM Kasahara Tatsuhito
> > <kasahara.tatsuhito@gmail.com> wrote:
> >>
> >> Hi.
> >>
> >> In the code in src/backend/replication/logical/origin.c,
> >> the error code "ERRCODE_CONFIGURATION_LIMIT_EXCEEDED" is given
> >> when a checksum check results in an error,
> >> but "ERRCODE_ DATA_CORRUPTED" seems to be more appropriate.
> >>
> >
> > +1. Your observation looks correct to me and the error code suggested
> > by you seems appropriate. We use ERRCODE_DATA_CORRUPTED in
> > ReadTwoPhaseFile() for similar error.
>
> Agreed, +1 for changing this.
>

I think we need to backpatch this till 9.6 as this is introduced by
commit 5aa2350426. Any objections to that?

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [PATCH] Tab completion for ALTER TABLE … ADD …
Next
From: Amit Kapila
Date:
Subject: Re: Skipping logical replication transactions on subscriber side