MIME-Version: 1.0
References: <CAGbX52GXtCZL0r2daozEwJH-tcH9bScxGit5D5syzizpJNwhSQ@mail.gmail.com>
In-Reply-To: <CAGbX52GXtCZL0r2daozEwJH-tcH9bScxGit5D5syzizpJNwhSQ@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Wed, 11 Sep 2024 09:19:37 -0400
Message-ID: <CAKAnmmLH0_XCsgNg=Nk_u3jZN_C=rmKFnTxvUju+HOBOjwm6iA@mail.gmail.com>
Subject: Re: Logical replication without direct link between publisher and subscriber?
To: Koen De Groote <kdg.dev@gmail.com>
Cc: PostgreSQL General <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000b469f90621d7d9d9"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmmLH0_XCsgNg%3DNk_u3jZN_C%3DrmKFnTxvUju%2BHOBOjwm6iA%40mail.gmail.com>
Precedence: bulk

--000000000000b469f90621d7d9d9
Content-Type: text/plain; charset="UTF-8"

>
> 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

--000000000000b469f90621d7d9d9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dumping =
changes periodically, sending them directly or uploading to cloud storage a=
nd then downloading and applying them on the subscriber side.<br>But maybe =
there&#39;s a simpler option someone here knows about?</blockquote><div><br=
></div><div>How about using WAL shipping to populate a replica, and either =
query that directly or use that as the publisher=C2=A0to your sequestered n=
ode?</div><div><br></div><div>Cheers,</div><div>Greg</div><div><br></div></=
div>

--000000000000b469f90621d7d9d9--