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 1uaWpE-006PWf-3o for pgsql-general@arkaria.postgresql.org; Sat, 12 Jul 2025 09:47:20 +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 1uaWpC-008Ieo-6R for pgsql-general@arkaria.postgresql.org; Sat, 12 Jul 2025 09:47:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uaHj1-006hg7-V6 for pgsql-general@lists.postgresql.org; Fri, 11 Jul 2025 17:39:56 +0000 Received: from mail-ej1-x62e.google.com ([2a00:1450:4864:20::62e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uaHiz-00741f-38 for pgsql-general@postgresql.org; Fri, 11 Jul 2025 17:39:56 +0000 Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-ae0b6532345so620221366b.1 for ; Fri, 11 Jul 2025 10:39:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1752255591; x=1752860391; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=/N8YMdUNLaSQymU0WJlJHih9reIyBax55YLrxsmNIhw=; b=AL4nxLW0T7Zb38+ErJ7TVZySxqFVWnCXeOxuynkfYKpFuLq2t/8gdVps1CQ9QI59UT baSrsaozeB6r7TjbX2leSyY6eWbpRNA301lEq/axrId9DA9RJqkWu9QpWWu8cxlm/GbY S3NPJU3x+c4QNwE+sPDH+JaKVpgL5IxQeEWhmtRKP51y0Pz/pW61FjmrQSleWoXWMKOn KENYmJNEKh4Lq62y1K6BFt2NhLDk6QPyXe/jLY9ZP0alRZXRDl7TUVwplpaR2bYUpGXY GkXpq5y/tDATme3o+CkQOmHnREQ9ESEmL9+Aj4goGWp/1EqXIc+HejG6l8w0WMJB0mXF oxkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1752255591; x=1752860391; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=/N8YMdUNLaSQymU0WJlJHih9reIyBax55YLrxsmNIhw=; b=i2Kov20ICMF+UgWnaLcFVTEWs6uCVIprAlolHBhYOyy+XGtF/1gjYHeAphGAI7rCqz 89NrQvifIHW1xw/6Z6cJzbdKMlMPSkU3LPklwNvOgDMUvf80loThm0Y1SFAH5pvFUTYy IZsKKXe+cKgYR/njYTGmmROc4dB1cccQAPjwWcCiujBL+WP9ErvQ5sk20ppFn7ALE2Ph KUX/pclW5oclS4j4f1IXNPGrQsWCeZPUJvIO+02WEiTd5CbtTbAVzV7SGiD1gFfWXrti C8UOXGVhjHqr18vqgtoMuX80UHOnojL1Q10q4sgevViK/WZWuFFmEqSVyXyhG9oTDr5E 5eTQ== X-Gm-Message-State: AOJu0YzFoNtDCDg76bxASDydTlOYdqwbAT4K3EPrPpzdadCO+U3AUdK0 oR4lGXmjSVitw3WkrLWV2EraJFbwNFAecvOuLwDD9utEXWxX+nqI5GRy3t5woqOy3Z3pp4Ek1pR QizhyEtURm0VmmrxTW61ZisDABducvVIqjCQs X-Gm-Gg: ASbGncvkNojZujb6BfWIoN2LRci1zrBsAw5gDmz4II7zmQ7o+55jSs7siuFtbjdsX85 d/Uq/hlxSbRpD+75YbSYipL/L/4o3ioRhWhpZ5OtuDeleS/DqCY8DaF62ucj6sDvpfgZDkn5TB1 YGAseUh+xFYpuKanarsSALG43btbiOhXMrxBZ8Z+3REpaEfwQXsPGbhT85MEXZVScLEQA585a6f nZy3Ozgf2rHS6YBEwFK6LanXYBlbR6AOF3MGgAfXw== X-Google-Smtp-Source: AGHT+IFlTFT7HpZrIBDItxH6zoiHTmtfzBiy2w63HBb1Ys9aSvb2iW4piOa6RrA+4sQN1ZHG7EWL2EXZMJGYLPWBF5o= X-Received: by 2002:a17:907:2d20:b0:ae6:d48e:f18d with SMTP id a640c23a62f3a-ae6e22e3f73mr925466366b.12.1752255590816; Fri, 11 Jul 2025 10:39:50 -0700 (PDT) MIME-Version: 1.0 From: Kiran K V Date: Fri, 11 Jul 2025 23:09:38 +0530 X-Gm-Features: Ac12FXwUIr0gReHFNtyWA5giCn2IsxFrf0MEBYtgviAKcGDsHqlZy9dp-mrrvEI Message-ID: Subject: Query regarding support of test_decoding and PGReplicationStream with Standby Logical Replication To: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="0000000000000be1f30639aaccd8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000be1f30639aaccd8 Content-Type: text/plain; charset="UTF-8" Hi, I have a question regarding the new feature introduced in PostgreSQL 16 that enables logical replication from a standby server. Currently, we are using a standalone instance of PostgreSQL 16 and performing logical replication by creating replication slots and utilizing the JDBC replication stream API (PGReplicationStream) with the test_decoding plugin. Could you please confirm whether this approach of logical replication is supported from a standby system? Specifically, does the standby system support the test_decoding plugin and the JDBC PGReplicationStream API for streaming changes ? Reference to JDBC Logical replication - https://jdbc.postgresql.org/documentation/server-prepare/#example-96-create-logical-replication-stream Regards, Kiran --0000000000000be1f30639aaccd8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,=C2=A0

I have a question = regarding the new feature introduced in PostgreSQL 16 that enables logical = replication from a standby server.

Currently, we are using a standalone instance of PostgreSQL 16 and performing=20 logical replication by creating replication slots and utilizing the JDBC replication stream API (PGReplicationStream)=C2=A0 with the test_decoding= =20 plugin.

Could you please confirm whether this approach of logical replication is supported from a standby system? Specifically, does the=20 standby system support the test_decoding plugin and the JDBC=20 PGReplicationStream API for streaming changes ?


Regards,
Kiran

--0000000000000be1f30639aaccd8--