On Thu, Apr 23, 2020 at 2:28 PM Erik Rijkers <e...@xs4all.nl> wrote: > > On 2020-04-23 05:24, Dilip Kumar wrote: > > On Wed, Apr 22, 2020 at 9:31 PM Erik Rijkers <e...@xs4all.nl> wrote: > >> > >> The 'ddl' one is apparently not quite fixed - I get this in (cd > >> contrib; make check)' (in both assert-enabled and non-assert-enabled > >> build) > > > > Can you send me the contrib/test_decoding/regression.diffs file? > > Attached.
So from regression.diff, it appears that in failing in memory allocation (+ERROR: invalid memory alloc request size 94119198201896). My colleague tried to reproduce this in a different environment but there is no success so far. One more thing surprises me is that after (v15-0011-Provide-new-api-to-get-the-streaming-changes.patch) actually, it should never go for the streaming path. However, we can not ignore the fact that some of the changes might impact the non-streaming path as well. Is it possible for you to somehow stop or break the code and send the stack trace? One idea is by seeing the log we can see from where the error is raised i.e MemoryContextAlloc or palloc or some other similar function. Once we know that we can convert that error to an assert and find the call stack. -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
