Re: Assertion failure while streaming toasted data
Pavan Deolasee <pavan.deolasee@gmail.com>
From: Pavan Deolasee <pavan.deolasee@gmail.com>
To: Dilip Kumar <dilipbalaut@gmail.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-05-25T14:03:31Z
Lists: 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
Commits
-
Fix assertion during streaming of multi-insert toast changes.
- 6f4bdf81529f 14.0 landed