On 2015-05-29 12:08:24 -0700, Josh Berkus wrote:
> Now, BDR is good because it sets an application_name which lets me
> figure out what's using the replication slot. But that's by no means
> required; other LC plug-ins, I expect, do not do so. So there's no way
> for the user to figure out which replication connection relates to which
> slots, as far as I can tell.
>
> In this test, it's easy because there's only one replication connection
> and one slot. But imagine the case of 14 replication connections with
> their own slots. How could you possibly figure out which one was the
> laggy one?
9.5 shows the pid.