From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
---|---|
To: | "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [BUG] "FailedAssertion" reported when streaming in logical replication |
Date: | 2021-04-29 10:53:41 |
Message-ID: | CAFiTN-vSkFerp1TjmkzscO5EcXUo8ZmcjtEuSgBVz3zPqYLkmA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 29, 2021 at 12:09 PM tanghy(dot)fnst(at)fujitsu(dot)com
<tanghy(dot)fnst(at)fujitsu(dot)com> wrote:
>
>
> On Thursday, April 29, 2021 3:18 PM, Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote
>
> >I tried to think about how to write a test case for this scenario, but
> >I think it will not be possible to generate an automated test case for this.
> >Basically, we need 2 concurrent transactions and out of that,
> >we need one transaction which just has processed only one change i.e
> >XLOG_HEAP2_NEW_CID and another transaction should overflow the logical
> >decoding work mem, so that we select the wrong transaction which
> >doesn't have the base snapshot. But how to control that the
> >transaction which is performing the DDL just write the
> >XLOG_HEAP2_NEW_CID wal and before it writes any other WAL we should
> >get the WAl from other transaction which overflows the buffer.
>
> Thanks for your updating.
> Actually, I tried to make the automated test for the problem, too. But made no process on this.
> Agreed on your opinion " not be possible to generate an automated test case for this ".
Thanks for trying this out.
> If anyone figure out a good solution for the test automation of this case.
> Please be kind to share that with us. Thanks.
+1
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2021-04-29 10:56:44 | function for testing that causes the backend to terminate |
Previous Message | Magnus Hagander | 2021-04-29 10:40:34 | Re: [PATCH] We install pg_regress and isolationtester but not pg_isolation_regress |