| From: | Koen De Groote <kdg(dot)dev(at)gmail(dot)com> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Logical replication without direct link between publisher and subscriber? |
| Date: | 2024-09-12 18:47:21 |
| Message-ID: | CAGbX52G=Fo8YhJ9o1te=G9FD9Yedpk_O55rSk8PqfFwy4SEsmw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 PM Greg Sabino Mullane <htamfids(at)gmail(dot)com>
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
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Moench-Tegeder | 2024-09-12 19:30:44 | Re: Better way to process records in bash? |
| Previous Message | Tom Lane | 2024-09-12 17:38:11 | Re: post-bootstrap init : permission denied pg_description |