RE: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13
Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
From: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
To: 'Braulio Fdo Gonzalez' <brauliofg@gmail.com>
Cc: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2025-06-10T02:09:22Z
Lists: pgsql-bugs
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 https://www.postgresql.org/message-id/CALDaNm2sGfKsZwm8rG132N_i0AvyxkYu8TL46kNcx7KwAUABxA%40mail.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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix re-distributing previously distributed invalidation messages during logical decoding.
- d87d07b7ad3b 18.0 landed
- 45c357e0e85d 17.6 landed
- b2ae077205e1 16.10 landed
- fc0fb77c550f 15.14 landed
- 983b3636259b 14.19 landed
- 1230be12f086 13.22 landed