Re: [BUG]Update Toast data failure in logical replication

From: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
To: "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com>
Cc: Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [BUG]Update Toast data failure in logical replication
Date: 2021-06-04 04:08:13
Message-ID: CAFiTN-t2k-DOuuvc7iSO5ZvGWhaYEVmFXvF3Z=rqPzt8dRyYrQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 4, 2021 at 8:25 AM tanghy(dot)fnst(at)fujitsu(dot)com
<tanghy(dot)fnst(at)fujitsu(dot)com> wrote:
>
> On Thu, Jun 3, 2021 7:45 PMDilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
> >
> > I have fixed all the pending issues, I see there is already a test
> > case for this so I have changed the output for that.
>
> Thanks for your patch. I tested it for all branches(10,11,12,13,HEAD) and all of them passed.(This bug was introduced in PG-10.)
> I also tested the scenario where I found this bug, data could be synchronized after your fix.

Thanks for verifying this.

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2021-06-04 04:28:05 Re: Are we missing (void) when return value of fsm_set_and_search is ignored?
Previous Message Masahiko Sawada 2021-06-04 03:28:46 Re: Transactions involving multiple postgres foreign servers, take 2