| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Braulio Fdo Gonzalez' <brauliofg(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13 |
| Date: | 2025-06-10 02:09:22 |
| Message-ID: | OSCPR01MB149660C87F3FEC011D6FD9054F56AA@OSCPR01MB14966.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-06-10 05:45:59 | Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements |
| Previous Message | Tom Lane | 2025-06-10 00:40:38 | Re: BUG #18907: SSL error: bad length failure during transfer data in pipeline mode with libpq |