Re: Assertion failure while streaming toasted data - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Assertion failure while streaming toasted data
Date
Msg-id CAFiTN-tSLYQSF6Y9UkMe6j5LE6SbSPoZgJufdu0jBBPKdHWfBA@mail.gmail.com
Whole thread Raw
In response to Re: Assertion failure while streaming toasted data  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Assertion failure while streaming toasted data
List pgsql-hackers
On Tue, May 25, 2021 at 4:50 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> Your patch will fix the reported scenario but I don't like the way
> multi_insert flag is used to detect incomplete tuple. One problem
> could be that even when there are no toast inserts, it won't allow to
> stream unless we get the last tuple of multi insert WAL. How about
> changing the code such that when we are clearing the toast flag, we
> additionally check 'clear_toast_afterwards' flag?

Yes, that can be done, I will fix this in the next version of the patch.

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



pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: Possible pointer var TupleDesc rettupdesc used not initialized (src/backend/optimizer/util/clauses.c)
Next
From: Masahiko Sawada
Date:
Subject: Re: Skipping logical replication transactions on subscriber side