Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13

Dear Braulio,

Hi, I'm having the issue with PG 15.13. We tried adding more memory
(logical_decoding_work_mem) to 5 GB, but it still doesn't work, and the process
"replicate" stops with the following error:
"CDC Fetch Failed: An unexpected connection error occurred while attempting to
replicate data from the source. Make sure your connection profile settings are
correct. If the problem persists, contact Google Support."
"ERROR: Invalid memory allocation request, size 1674007328."
We have another environment with PG 15.12, and it works perfectly.
This case has have relation with /messages/by-id/CALDaNm2sGfKsZwm8rG132N_i0AvyxkYu8TL46kNcx7KwAUABxA@mail.gmail.com

Thanks for reporting. Yes, I also feel that you faced the same issue. Since the
issue happens lower layer than the logical decoding, logical_decoding_work_mem
can't work to avoid the ERROR. We are discussing how we fix.

Best regards,
Hayato Kuroda
FUJITSU LIMITED

On Mon, Jun 9, 2025 at 7:09 PM Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:

Dear Braulio,

Hi, I'm having the issue with PG 15.13. We tried adding more memory
(logical_decoding_work_mem) to 5 GB, but it still doesn't work, and the process
"replicate" stops with the following error:
"CDC Fetch Failed: An unexpected connection error occurred while attempting to
replicate data from the source. Make sure your connection profile settings are
correct. If the problem persists, contact Google Support."
"ERROR: Invalid memory allocation request, size 1674007328."
We have another environment with PG 15.12, and it works perfectly.
This case has have relation with /messages/by-id/CALDaNm2sGfKsZwm8rG132N_i0AvyxkYu8TL46kNcx7KwAUABxA@mail.gmail.com

Thanks for reporting. Yes, I also feel that you faced the same issue. Since the
issue happens lower layer than the logical decoding, logical_decoding_work_mem
can't work to avoid the ERROR. We are discussing how we fix.

And I pushed the fix for this issue[1]https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=d87d07b7ad3b782cb74566cd771ecdb2823adf6a.

Regards,

[1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=d87d07b7ad3b782cb74566cd771ecdb2823adf6a

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

Hi, will this be fixed in 15.14?

El mar, 17 jun 2025 a las 13:45, Masahiko Sawada (<sawada.mshk@gmail.com>)
escribió:

On Mon, Jun 9, 2025 at 7:09 PM Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:

Dear Braulio,

Hi, I'm having the issue with PG 15.13. We tried adding more memory
(logical_decoding_work_mem) to 5 GB, but it still doesn't work, and

the process

"replicate" stops with the following error:
"CDC Fetch Failed: An unexpected connection error occurred while

attempting to

replicate data from the source. Make sure your connection profile

settings are

correct. If the problem persists, contact Google Support."
"ERROR: Invalid memory allocation request, size 1674007328."
We have another environment with PG 15.12, and it works perfectly.
This case has have relation with

/messages/by-id/CALDaNm2sGfKsZwm8rG132N_i0AvyxkYu8TL46kNcx7KwAUABxA@mail.gmail.com

Thanks for reporting. Yes, I also feel that you faced the same issue.

Since the

issue happens lower layer than the logical decoding,

logical_decoding_work_mem

can't work to avoid the ERROR. We are discussing how we fix.

And I pushed the fix for this issue[1].

Regards,

[1]
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=d87d07b7ad3b782cb74566cd771ecdb2823adf6a

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

--

On Sun, Jun 29, 2025 at 12:29 PM Braulio Fdo Gonzalez
<brauliofg@gmail.com> wrote:

Hi, will this be fixed in 15.14?

Yes, the fix will be included in the next minor versions, 15.14.

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com