Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 - Mailing list pgsql-bugs

From Amit Kapila
Subject Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
Date
Msg-id CAA4eK1JjGrMsLoMdCynBLkPW5oTPsgpZKyJTP1g6YV+mmV-zWw@mail.gmail.com
Whole thread Raw
In response to Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5  (vignesh C <vignesh21@gmail.com>)
Responses Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
List pgsql-bugs
On Sun, Jun 22, 2025 at 8:28 AM vignesh C <vignesh21@gmail.com> wrote:
>
> On Fri, 20 Jun 2025 at 13:51, Hayato Kuroda (Fujitsu)
> <kuroda.hayato@fujitsu.com> wrote:
> >
>
> > To fix the test failure, I suggest to just remove the case. Insert-after-commit
> > case has already been tested by above part of this file, so no need to do others.
>
> Alternatively I was thinking of a fix if it is possible to run this
> test conditionally when CLOBBER_CACHE_ALWAYS is not defined, I was not
> sure if it is easy to do that and worth the effort for the PG13
> branch. I'm ok with the proposed change.
>

I prefer to change the test because, if the above analysis is correct,
it indicates that the test has a cache flush hazard. It would be
better to make the test robust instead of working around it.

--
With Regards,
Amit Kapila.



pgsql-bugs by date:

Previous
From: vignesh C
Date:
Subject: Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
Next
From: Masahiko Sawada
Date:
Subject: Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5