Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
От | vignesh C |
---|---|
Тема | Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 |
Дата | |
Msg-id | CALDaNm0=KzQ8TTwTwSgZgvYwccWJU9rpFwTZYNFE1zAFLtSw3g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 (Alexander Lakhin <exclusion@gmail.com>) |
Ответы |
RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
|
Список | pgsql-bugs |
On Fri, 20 Jun 2025 at 10:30, Alexander Lakhin <exclusion@gmail.com> wrote: > > Hello Sawada-san, > > 17.06.2025 20:40, Masahiko Sawada wrote: > > Pushed the fix (d87d07b7ad3). Thank you for working on this fix. > > > As buildfarm [1] shows, the test case added to invalidation_distribution > with 1230be12f fails against -DCLOBBER_CACHE_ALWAYS on REL_13_STABLE: > diff -U3 /home/buildfarm/trilobite/buildroot/REL_13_STABLE/pgsql.build/contrib/test_decoding/expected/invalidation_distribution.out /home/buildfarm/trilobite/buildroot/REL_13_STABLE/pgsql.build/contrib/test_decoding/output_iso/results/invalidation_distribution.out > --- /home/buildfarm/trilobite/buildroot/REL_13_STABLE/pgsql.build/contrib/test_decoding/expected/invalidation_distribution.out 2025-06-17 10:24:24.382768613 +0200 > +++ /home/buildfarm/trilobite/buildroot/REL_13_STABLE/pgsql.build/contrib/test_decoding/output_iso/results/invalidation_distribution.out 2025-06-17 15:01:53.921913314 +0200 > @@ -31,7 +31,7 @@ > step s2_get_binary_changes: SELECT count(data) FROM pg_logical_slot_get_binary_changes('isolation_slot', NULL, NULL, 'proto_version','1', 'publication_names', 'pub') WHERE get_byte(data, 0) = 73; > count > ----- > - 0 > + 1 > (1 row) > > ?column? > > I could reproduce this locally and also checked that the test passes on > REL_14_STABLE and master. > > Could you look at this, please? Thanks for reporting this, we will analyse this and provide a fix for this. Regards, Vignesh
В списке pgsql-bugs по дате отправления: