Re: viewing connectioninfo used by subscriber on the publication server when inactive

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: Keith Fiske <keith(dot)fiske(at)crunchydata(dot)com>
Cc: Wim Bertels <wim(dot)bertels(at)ucll(dot)be>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: viewing connectioninfo used by subscriber on the publication server when inactive
Date: 2020-05-14 14:40:27
Message-ID: F3ECB264-D36F-476E-84D9-876ACBB8CF15@elevated-dev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> On May 14, 2020, at 8:34 AM, Keith Fiske <keith(dot)fiske(at)crunchydata(dot)com> wrote:
>
> But, again, I would still try and rethink this strategy.

For instance:

- single replication slot
- logical decoding locally that filters updates and records the relevant ones into a serialized updates table
- clients record their position in the updates table, ask for new updates on connect

Or, similar to above, but just use triggers on relevant tables.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Wim Bertels 2020-05-14 14:50:28 Re: viewing connectioninfo used by subscriber on the publication server when inactive
Previous Message Keith Fiske 2020-05-14 14:34:37 Re: viewing connectioninfo used by subscriber on the publication server when inactive