Re: Error code for checksum failure in origin.c
От | Amit Kapila |
---|---|
Тема | Re: Error code for checksum failure in origin.c |
Дата | |
Msg-id | CAA4eK1JS_fDvrTRJuFy7wQADZaKmaNGFC3na4wXQUWhfHhyj=w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Error code for checksum failure in origin.c (Daniel Gustafsson <daniel@yesql.se>) |
Ответы |
Re: Error code for checksum failure in origin.c
Re: Error code for checksum failure in origin.c Re: Error code for checksum failure in origin.c |
Список | 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 по дате отправления: