Re: viewing connectioninfo used by subscriber on the publicationserver when inactive

> On May 14, 2020, at 8:34 AM, Keith Fiske <keith.fiske@crunchydata.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.