Thread: Logical Replication 08P01 invalid memory alloc request size 1095736448
Hello All,
we have this set up :
Postgres 15.13 on RHEL 9.6
Logical Master also have 2 streaming replica
Logical Replica also have 1 streaming replica
Postgres 15.13 on RHEL 9.6
Logical Master also have 2 streaming replica
Logical Replica also have 1 streaming replica
We just do patch updates from 15.12 to 15.13, restart Logical Master and then Logical Replica, and suddenly Logical replication stops working. Streaming replication of both are fine.
The message on Logical Replica :
ERROR,08P01,"could not receive data from WAL stream: ERROR: invalid memory alloc request size 1095736448",,,,,,,,,"","logical replication worker",,0
The message on Logical Replica :
ERROR,08P01,"could not receive data from WAL stream: ERROR: invalid memory alloc request size 1095736448",,,,,,,,,"","logical replication worker",,0
The message on Logical Master :
"START_REPLICATION", LOG,00000,"starting logical decoding for slot ""_subscription""","Streaming transactions committing after 33D45/373C2D98, reading WAL from 33D44/EF3219B0.",,,,,"START_REPLICATION SLOT ""_subscription"" LOGICAL 33D45/373C2D98 (proto_version '3', publication_names '""_publication""')",,,"_subscription","walsender",,0
"START_REPLICATION", ,LOG,00000,"logical decoding found consistent point at 33D44/EF3219B0","Logical decoding will begin using saved snapshot.",,,,,"START_REPLICATION SLOT ""_subscription"" LOGICAL 33D45/373C2D98 (proto_version '3', publication_names '""_publication""')",,,"_subscription","walsender",,0
Checking at error code 08P01 is protocol_violation.
Is there any idea on what causing this and how to resolve ?
Regards,
Soni M <diptatapa@gmail.com> writes: > We just do patch updates from 15.12 to 15.13, restart Logical Master and > then Logical Replica, and suddenly Logical replication stops working. > Streaming replication of both are fine. This sounds like the same bug previously discussed in https://www.postgresql.org/message-id/flat/680bdaf6-f7d1-4536-b580-05c2760c67c6%40deepbluecap.com We'll have a fix in next month's quarterly releases. For the moment, you could either roll back to 15.12 or cherry-pick the fix at commit fc0fb77c5. regards, tom lane
Thanks Tom, really appreciate it.
On Sun, Jul 6, 2025 at 10:12 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Soni M <diptatapa@gmail.com> writes:
> We just do patch updates from 15.12 to 15.13, restart Logical Master and
> then Logical Replica, and suddenly Logical replication stops working.
> Streaming replication of both are fine.
This sounds like the same bug previously discussed in
https://www.postgresql.org/message-id/flat/680bdaf6-f7d1-4536-b580-05c2760c67c6%40deepbluecap.com
We'll have a fix in next month's quarterly releases. For the moment,
you could either roll back to 15.12 or cherry-pick the fix at
commit fc0fb77c5.
regards, tom lane
Regards,