On Fri, Apr 30, 2021 at 3:01 PM Amit Kapila <amit.kapil...@gmail.com> wrote: > > On Wed, Apr 28, 2021 at 11:03 AM Dilip Kumar <dilipbal...@gmail.com> wrote: > > > > On Wed, Apr 28, 2021 at 11:00 AM Amit Kapila <amit.kapil...@gmail.com> > > wrote: > > > > > > > The idea I have is to additionally check that we are decoding > > > streaming or prepared transaction (the same check as we have for > > > setting curtxn) or we can check if CheckXidAlive is a valid > > > transaction id. What do you think? > > > > I think a check based on CheckXidAlive looks good to me. This will > > protect against if a similar error is raised from any other path as > > you mentioned above. > > > > We can't use CheckXidAlive because it is reset by that time.
Right. So, I > used the other approach which led to the attached. The patch looks fine to me. -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
