pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Alexander Lakhin <exclusion@gmail.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
To: vignesh C <vignesh21@gmail.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>
Cc: Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
Cc: Duncan Sands <duncan.sands@deepbluecap.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
Date: Fri, 20 Jun 2025 08:00:00 +0300
Message-ID: <dbf561f7-465e-4086-adfa-733b9b9a34b3@gmail.com> (raw)
In-Reply-To: <CAD21AoBfFEG=y=sHrhOO-EWpcFW=PmXcFhkPGYF+O0AH+bRo6w@mail.gmail.com>
References: <680bdaf6-f7d1-4536-b580-05c2760c67c6@deepbluecap.com>
	<CAD21AoAvZ=8_in4NcdXcOWaHnBdch_R5NE7N+iOde2+7S2QuDw@mail.gmail.com>
	<OSCPR01MB14966456C004EB65B31FE72AAF56FA@OSCPR01MB14966.jpnprd01.prod.outlook.com>
	<CAD21AoCR5ULReGxM9VNsp91MamPYLNLM7oiWqizpb-gPSpicVg@mail.gmail.com>
	<CAA4eK1JVQfYKF8TfDuoZpQYRXq7siVn5k_4u270FMVGth1V_bw@mail.gmail.com>
	<CAD21AoCNNkLPoc+PWLGpZs74NwHxCvvffAjx6Yn3pJ2xJJPWtw@mail.gmail.com>
	<CALDaNm0DkWbr8eA3kAkEw+cZA-n=KPmFxZ_5bz_YDqhYQGk6iA@mail.gmail.com>
	<CALDaNm0TaTPuza7Fa+DRMzL+mqK3+7RVEvFiRoDJbU2vkJESwg@mail.gmail.com>
	<CAD21AoDRkvBQdFtHfro2zd7HxcCT4JSWGWfF68YU977mvu6oVg@mail.gmail.com>
	<CAD21AoDCphZ30iiMOG8mZH_eo40m_1KY=4gz7-Yd+9M3FRBySg@mail.gmail.com>
	<CALDaNm3m6Dq2d6bCBaOjnABYavT3p+=VbJd5oJKok0sCTOSZog@mail.gmail.com>
	<CAD21AoCHqKXVhUZbxPKBve-uEHJWKxV9SVC5deiB5VUONTH=6w@mail.gmail.com>
	<CALDaNm2udG-+nNnOfYYjC7pBVziZBRbJNPFq__Ynv3eASsZMAw@mail.gmail.com>
	<CAD21AoBfFEG=y=sHrhOO-EWpcFW=PmXcFhkPGYF+O0AH+bRo6w@mail.gmail.com>

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?

[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=trilobite&dt=2025-06-17%2008%3A24%3A00

Best regards,
Alexander

view thread (94+ messages)  latest in thread

Message-ID: <dbf561f7-465e-4086-adfa-733b9b9a34b3@gmail.com>
Permalink:  ../dbf561f7-465e-4086-adfa-733b9b9a34b3@gmail.com/
Also on:    postgresql.org/message-id/dbf561f7-465e-4086-adfa-733b9b9a34b3@gmail.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: exclusion@gmail.com, sawada.mshk@gmail.com, vignesh21@gmail.com, amit.kapila16@gmail.com, kuroda.hayato@fujitsu.com, duncan.sands@deepbluecap.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
  In-Reply-To: <dbf561f7-465e-4086-adfa-733b9b9a34b3@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox