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-006PWe-3u 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-008Iej-6M 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 1uaC5T-004Jcw-N8 for pgsql-general@lists.postgresql.org; Fri, 11 Jul 2025 11:38:44 +0000 Received: from mail-ej1-x632.google.com ([2a00:1450:4864:20::632]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uaC5R-0070y4-33 for pgsql-general@lists.postgresql.org; Fri, 11 Jul 2025 11:38:44 +0000 Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-ae0de0c03e9so340775566b.2 for ; Fri, 11 Jul 2025 04:38:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1752233919; x=1752838719; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=iruhCRVF9nUm6gTdPDUslrR53YWBSL27Imj1XHvpYLM=; b=U6Aj1fPLu+Wu/6DqWXey7oGj/JDa+IT29qdMhKUp+XkYArtSOhomkiBoy+AZhJMaKn Vs9+QSzsUnkVEAAloObBMyuwGl7uWAdHMxWt4jxKNQlvpK/BjUhkKk6FLNGMuzJnBg+R qOSlRi9A/ZI4zXyVj9Ai1juq4AhSCEnPJlsQYoETSZC2PxcJYq5A32aq2w3jb+HDfupp UiBYKyA6Zx+W8NbgwTJz5UuBSd/ZCNsRBuGlI1CZ9GcNShMLSkvHt3MOz1u6Sq4O8nBj U6icxZb+KQPjtgFHj4q7Cwf25PoVQJyJrwptf9P4clceHEGaspva5l/QeznjDTWJfzvv p7yQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1752233919; x=1752838719; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=iruhCRVF9nUm6gTdPDUslrR53YWBSL27Imj1XHvpYLM=; b=MtyCfgVb2nyKZmCMkCDoww5j8gyk++P/SGVWpZgvnKbeLuojuE7mCiMP0EnY2A8h3Y NEHOGbII3ciAd6ZoVpLGNV0Kh4pdzaxHwzxN0al3hmEJskNs5OkLVQARldj22MXNHhjT 39bEbpzYAKHFCfLSCdWFxiuHAfCy5E/tR0KTb3b2tp5nu60/pdsuDnefEjk3WNHSPdFD NRHx5w+ANdlISKRdF3Ou1DRT8ioyX78LDOUAywOfwgXkSGILCgSKROwI6H0EWy+x4krb JZIdtO412Qb3Cf2Qkade5/WBxq7ByOELBMjZ+F1FT8WWcnwoAKbG25hdplpCPXaFo8iD q/tQ== X-Gm-Message-State: AOJu0YyyZHWk9cfHVIyaBwAXM5wgfh3/XHFT+8GdCRA//hHkwZZizpDP Jd+yrr1aWeficuFMSAVavaewEdDgZVnthWaglDEjmvbpK0FtHv8LUIUHSrz9dfn5WJWAB2iATIE QtmSQ0gNseIuA3sW1sdFPB+MktcKXqENeyCmd X-Gm-Gg: ASbGncu/HtF06uUcyb/wA8Fp3fJYOKUTvKrDD5DwjfLK3YAiyoHMBakGKtC1MYsmjrx CHkLPsodR+A69l3zUpAv0IGSB9j52sIVOS6vjOqUsWI5P2W5fmxK+eTWYOgJBF6CtqCnQcU19rx 7xvui5djpg0RoL1VJuiCGGRyfPwxGLKi8fxYTZmxVAe47/S7PZu8aJb9k4I2/K0+/WY8QSR0flJ 1sjG36gNVN/2kuL+KrkRGV0FYkrO5tSTXNJWTGOHgjZBkuKrFUo X-Google-Smtp-Source: AGHT+IHSJRGIwVq3rFvKrq2oRL/2jcNiQ5G+q8+Wh1RCuN+EjWCL9L+PgS7qi1Sc+WhffqUxODFDfiXGDPp9PQQqzY4= X-Received: by 2002:a17:907:d7cb:b0:ae0:d7c7:97ee with SMTP id a640c23a62f3a-ae6fc0af170mr297468366b.41.1752233918328; Fri, 11 Jul 2025 04:38:38 -0700 (PDT) MIME-Version: 1.0 From: Kiran K V Date: Fri, 11 Jul 2025 17:08:26 +0530 X-Gm-Features: Ac12FXyLr0rFowjfd_-r6Lf5Xg_W-wZPLpZ0WXkaRYM4jIR82lMOprLAE4iLKpo Message-ID: Subject: Query regarding support of test_decoding and PGReplicationStream with Standby Logical Replication To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000043f47b0639a5c0a0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000043f47b0639a5c0a0 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 --00000000000043f47b0639a5c0a0 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 stand= alone instance of PostgreSQL 16 and performing logical replication by creat= ing replication slots and utilizing the JDBC replication stream API (PGRepl= icationStream)=C2=A0 with the test_decoding plugin.

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

Regards,
Kiran
--00000000000043f47b0639a5c0a0--