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 1sooqz-00E2P1-J4 for pgsql-general@arkaria.postgresql.org; Thu, 12 Sep 2024 18:47:42 +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 1sooqy-00Ep74-TK for pgsql-general@arkaria.postgresql.org; Thu, 12 Sep 2024 18:47:40 +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 1sooqy-00Ep39-HI for pgsql-general@lists.postgresql.org; Thu, 12 Sep 2024 18:47:40 +0000 Received: from mail-ej1-x634.google.com ([2a00:1450:4864:20::634]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sooqv-000qQx-Ni for pgsql-general@lists.postgresql.org; Thu, 12 Sep 2024 18:47:39 +0000 Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-a8d6d0fe021so201219466b.1 for ; Thu, 12 Sep 2024 11:47:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726166855; x=1726771655; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=fisLOW+cUrjSUCewMRxz5BCWYoYAawovJsuH9OU6bJ4=; b=XKXDuHtI1i2kjWr0djd8m60ebeOqoOL1jWlZYAfMdrdBs17GlFlsJaj5r2uNQI/YhX u/JrJ+TE9QQhdd6XU7QODpgoaGD2569frcBVDep/OZLYqKnBIwSWA4lymlJ6wTwFdhlr sRuyNsAEAxBzNFiAgO6B2HwcjPtcNvXwchy1cmKVxJX/nBB2K7pLTOMk4vll5NSOK6dK X76NdgMVxvkSiy0aDSRZA4tQpiTD/k5r5pxw0+56heClDinWF8vQYr8XV4qr/9dqGuiu gF678qWTZWIWs5M8R//sWgIktjHTnZcz4e55j3c8cyV6xZTqCe1KUfg5kBLiG8fopIYB XB8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726166855; x=1726771655; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=fisLOW+cUrjSUCewMRxz5BCWYoYAawovJsuH9OU6bJ4=; b=cWVpsj47vH8NTvPmKFd9hveCvIvxmvUR4I3ysbis9009GKdX+A+DClqXxlAyW6CpCJ oO6aAAVuEqJqzJ1fPkB5RgM0zVC7NHbdIP8dhlbcLSbsYz6V9kYiCOFDCer8F4OaSTZ3 4wQY1u0SvKZJmZi8cwCzoElNAXZ/RcuMgSdRK6Mobu1fRtDJMI6BcVmwq+heWaDpEzxh jBoP36DrWrubHs5P56ePsJhwaKNPBEhGJbU2sswtN9vcIok3jgAvI2CaxJnTD4I30TjJ IqfDJ3yxdPVDzfRDpzeLvIYp22pr8JISHJgWNzdboY29bh+Jlcx2MxLnrpfjnyMyDQIx ZOOw== X-Gm-Message-State: AOJu0YyVh6A8ObFUBVzjPtXUt5iBnsCUCGGDITl5xbK1560xynIaeKVK UrzXa3WoYmo4JAu50C5x6O8n2kuNxGVxiFLvXTGdZAJs0HnZiCtvCPfse5F8jmM1N0tx/eiOqUJ atny28grD+m2XH1t9P/J1cRC8XAE= X-Google-Smtp-Source: AGHT+IEt1NMyvrpWBZn4HJYQ2h6P1KYgAy3wWHHX4p2z8DlU6r5iospVWHvF/neCaytd2tt1QfTkxEtJMU68oDjBkgc= X-Received: by 2002:a17:906:d7c7:b0:a8d:2faf:d337 with SMTP id a640c23a62f3a-a90293dc1ddmr386935966b.7.1726166854746; Thu, 12 Sep 2024 11:47:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Koen De Groote Date: Thu, 12 Sep 2024 20:47:21 +0200 Message-ID: Subject: Re: Logical replication without direct link between publisher and subscriber? To: Greg Sabino Mullane Cc: PostgreSQL General Content-Type: multipart/alternative; boundary="0000000000003352f90621f08ad4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003352f90621f08ad4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I've considered it, but it sounds like a lot of work and failure prone. Even projects like Debezium seem like it's a ton to set up. Thanks for the suggestions. Regards, Koen On Wed, Sep 11, 2024 at 3:20=E2=80=AFPM Greg Sabino Mullane wrote: > Dumping changes periodically, sending them directly or uploading to cloud >> storage and then downloading and applying them on the subscriber side. >> But maybe there's a simpler option someone here knows about? > > > How about using WAL shipping to populate a replica, and either query that > directly or use that as the publisher to your sequestered node? > > Cheers, > Greg > > --0000000000003352f90621f08ad4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I've considered it, but it sounds lik= e a lot of work and failure prone. Even projects like Debezium seem like it= 's a ton to set up.

Thanks for the= suggestions.

Regards,
Koen
On Wed, S= ep 11, 2024 at 3:20=E2=80=AFPM Greg Sabino Mullane <htamfids@gmail.com> wrote:
Dumping changes periodically, sending them dire= ctly or uploading to cloud storage and then downloading and applying them o= n the subscriber side.
But maybe there's a simpler option someone he= re knows about?

How about using WAL shippin= g to populate a replica, and either query that directly or use that as the = publisher=C2=A0to your sequestered node?

Cheers,
Greg

--0000000000003352f90621f08ad4--