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

From Pavan Deolasee
Subject Re: Assertion failure while streaming toasted data
Date
Msg-id CABOikdO1nLhOGq9yXppW66ZhOGHu1wAgyA0tRYoYOZe7LwKLNw@mail.gmail.com
Whole thread Raw
In response to Re: Assertion failure while streaming toasted data  (Dilip Kumar <dilipbalaut@gmail.com>)
List pgsql-hackers


On Tue, May 25, 2021 at 6:55 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
On Tue, May 25, 2021 at 6:50 PM Pavan Deolasee <pavan.deolasee@gmail.com> wrote:

> 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.
>
Yes, it is reproducing without fix, I already tested it.  Basically, I
am using the "stream_test" table in "copy stream_test to stdout""
command which already has 20 toasted tuples, each of size 6000 bytes
so that is big enough to cross 64kB.


Ok, great! Thanks for confirming.

Thanks,
Pavan 

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

pgsql-hackers by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: pg_rewind fails if there is a read only file.
Next
From: Amit Langote
Date:
Subject: Re: Skip partition tuple routing with constant partition key