| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Pavan Deolasee <pavan(dot)deolasee(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:24:50 |
| Message-ID: | CAFiTN-ueN+j6Sq+13TfkFCdCqCk1b3GoDvMGyRm7FjGGU9kYoQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 25, 2021 at 6:50 PM Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)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.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-05-25 13:38:31 | Re: Refactor "mutually exclusive options" error reporting code in parse_subscription_options |
| Previous Message | Pavan Deolasee | 2021-05-25 13:20:10 | Re: Assertion failure while streaming toasted data |