Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uYLs2-004vsg-E5 for pgsql-general@arkaria.postgresql.org; Sun, 06 Jul 2025 09:41:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uYLrz-00CflF-Bh for pgsql-general@arkaria.postgresql.org; Sun, 06 Jul 2025 09:41:11 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uYLrz-00Cfl6-0c for pgsql-general@lists.postgresql.org; Sun, 06 Jul 2025 09:41:11 +0000 Received: from mail-ej1-x629.google.com ([2a00:1450:4864:20::629]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uYLrw-005qiK-0L for pgsql-general@postgresql.org; Sun, 06 Jul 2025 09:41:10 +0000 Received: by mail-ej1-x629.google.com with SMTP id a640c23a62f3a-ae0d7b32322so323654066b.2 for ; Sun, 06 Jul 2025 02:41:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1751794866; x=1752399666; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=gJmsnrpmlUtPXsfi3jqujMFz2/n4GURZ557iCGBHPF4=; b=CXWYybbhycZDSDd19lIYex3BwePzoLal2D4UfF8FmHsfeFM6FwhXElAkgaLAiejSxu p5NQsxbdlihI0sUTyEgcZEWI2WbFvqZY+YX6yfE3UTy7Ar/ZNxcJ0tnfgkF1c0oBuksi jB9xJ5sQEHoSOqk/7La5Pdo5nFMtVrybb28e8g/oRaggCxgaeCB6KoMp2DplBv8t5iWV Ac+u0FkasOhBr61BOVUprAPa/CXGzLeIe+5x8oFIpa/jgSpjtt68yf21VJ9O8fUwz9kI iUMUTQif2DxugS94FqkosE6ZyqKyeSTUXcmBLxcj/tw5BYr25zLPWHbIIaEDBSTSIz2H 1rZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1751794866; x=1752399666; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=gJmsnrpmlUtPXsfi3jqujMFz2/n4GURZ557iCGBHPF4=; b=fo7c7hnCi1qV5mwSQQhpt51relL0Q9yPiuzqLfM4y5GORiN1+d9GdFLoEk6uc05UmX 0Cntoo/hvv0LtrZ7opIKaypk4diNemBkhRizM42aCXls+LJ23N/+KIQBjwPhwaZkNt8j +NPrzbTJs2kzyzt1bXzrynmNNMO5rq4tHqjEAA/fpftb0z/X+e2uVPUOB1PtlJO+m+Vr CpgFrRmtlNbN3jRYVjcq9mfNtJRpceP57xei7tNOyzqT1miczZkvBB0Ieyo+AwsZRZoV jCz66CloRZzwzbJ20jerwRpcr5T4GK89v83B84ZhOAdknRpdQwhx4qp5rapoZD84QDwf QtvQ== X-Gm-Message-State: AOJu0YzZIO+ct0quAJ+Rw4bsXsU6QW+/dZ+DuHRgu2kKcljB6XqE6Lfo bnrsz54MzToJxjCcmd0bmTOOO5EX05pOnBUV2cw8UN7NS9apox6ogwo0cubyqXcXFOohuH52k15 N9kj4S6IoMbDn34isGBsP7/U5SIGOm8zVIoVx X-Gm-Gg: ASbGncsJBHscr+c7e4l34sjKg/OEWLQqmLKj6/SbHatt15rgfvARldSe8kkRC+KsOXq ZcrmPMv7gn2Bz99ypon+t4hUu+q40d64Kgyiz1448gSst+AQg10swKasCQTcSCEbj3bNTl17B5S 6yMuaY0Sni0aWGNPVXJaBtQnuW+tNWfiFOvDA1oytl9GGVlYbFzbDVZa4= X-Google-Smtp-Source: AGHT+IF1qN+SHng4bhfEJkx0pwh01YAnxxIZhU8ILgm4xxS2l48NA4MOuVqZazTMgoiN7DkxYjwBNVB+oyfMY1mmmdk= X-Received: by 2002:a17:907:961f:b0:ae0:ab3f:36b5 with SMTP id a640c23a62f3a-ae3fe457c8cmr902735966b.4.1751794866119; Sun, 06 Jul 2025 02:41:06 -0700 (PDT) MIME-Version: 1.0 From: Soni M Date: Sun, 6 Jul 2025 16:40:55 +0700 X-Gm-Features: Ac12FXzf43Vd_vQUXE34oGzbp8Ht_lqqUhGf-Rs05p8vSgyVq6DMTQ7i1G2ywQY Message-ID: Subject: Logical Replication 08P01 invalid memory alloc request size 1095736448 To: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="000000000000b6e8ab06393f86a5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b6e8ab06393f86a5 Content-Type: text/plain; charset="UTF-8" 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 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 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 Maula Harriz --000000000000b6e8ab06393f86a5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello All,
we have this se= t up :
Postgres 15.13 on RHEL 9.6

Logical Master also have 2 stre= aming 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 wor= king. Streaming replication of both are fine.

The message on Logical= Replica :=C2=A0
ERROR,08P01,"could not receive data from WAL strea= m: ERROR: =C2=A0invalid memory alloc request size 1095736448",,,,,,,,,= "","logical replication worker",,0

=
The message on Logical Master :
"START_REPLICATION"= ;, LOG,00000,"starting logical decoding for slot ""_subscrip= tion""","Streaming transactions committing after 33D45/= 373C2D98, reading WAL from 33D44/EF3219B0.",,,,,"START_REPLICATIO= N SLOT ""_subscription"" LOGICAL 33D45/373C2D98 (proto_= version '3', publication_names '""_publication"&= quot;')",,,"_subscription","walsender",,0
<= br>
"START_REPLICATION", ,LOG,00000,"logical decod= ing found consistent point at 33D44/EF3219B0","Logical decoding w= ill begin using saved snapshot.",,,,,"START_REPLICATION SLOT &quo= t;"_subscription"" LOGICAL 33D45/373C2D98 (proto_version = 9;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 Maula Harriz
--000000000000b6e8ab06393f86a5--