Re: BUG #17055: Logical replication worker crashes when applying update of row that dose not exist in target partiti - Mailing list pgsql-bugs

From Amit Langote
Subject Re: BUG #17055: Logical replication worker crashes when applying update of row that dose not exist in target partiti
Date
Msg-id CA+HiwqF0xi2KmPYKPPCtcgQ2vnjQrfm5cdY50VRC+S_s1M4KvQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17055: Logical replication worker crashes when applying update of row that dose not exist in target partiti  (Michael Paquier <michael@paquier.xyz>)
Responses Re: BUG #17055: Logical replication worker crashes when applying update of row that dose not exist in target partiti  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Fri, Jun 11, 2021 at 3:26 PM Michael Paquier <michael@paquier.xyz> wrote:
> On Fri, Jun 11, 2021 at 02:56:58PM +0900, Amit Langote wrote:
> > Attached fixes the problem for me.  Not sure if adding a test case makes sense.
>
> It seems to me that it would make sense to have some coverage.  We've
> caught issues in the past in this area, particularly with buildfarm
> animals running CLOBBER_CACHE_ALWAYS.

I thought about it for a minute when writing the patch I posted, but
wasn't really sure what the test case would look like.  The only
external proof that the case worked correctly, AFAICS, is the DEBUG1
message that's written to the log.  How do we add a test case with
that?  I know you mentioned an idea before to check/grep the log for
such cases.  Is that how?

-- 
Amit Langote
EDB: http://www.enterprisedb.com



pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #17055: Logical replication worker crashes when applying update of row that dose not exist in target partiti
Next
From: Tom Lane
Date:
Subject: Re: BUG #17055: Logical replication worker crashes when applying update of row that dose not exist in target partiti