Re: Assertion failure while streaming toasted data

From: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Assertion failure while streaming toasted data
Date: 2021-05-25 13:20:10
Message-ID: CABOikdOFOtJbM0OO-WvfHZHQQXhYRpK65fcSrD8Aq6BcxwHLKg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 25, 2021 at 6:43 PM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:

>
> I have also added a test case for this.
>
>
Is that test good enough to trigger the original bug? In my experience, I
had to add a lot more tuples before the logical_decoding_work_mem
threshold was crossed and the streaming kicked in. I would suggest running
the test without the fix and check if the assertion hits. If so, we are
good to go.

Thanks,
Pavan

--
Pavan Deolasee
EnterpriseDB: https://www.enterprisedb..com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2021-05-25 13:24:50 Re: Assertion failure while streaming toasted data
Previous Message Dilip Kumar 2021-05-25 13:12:54 Re: Assertion failure while streaming toasted data