From: | Wim Bertels <wim(dot)bertels(at)ucll(dot)be> |
---|---|
To: | Keith Fiske <keith(dot)fiske(at)crunchydata(dot)com> |
Cc: | 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 12:33:24 |
Message-ID: | 5f77a6c973aaf8f9086cf42933f476e5bd9a948d.camel@ucll.be |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
>
>
> The replication slot connection could use any role that has been
> configured to allow replication. So there is no way to know which
> role is actually using a slot without it actually being connected.
> You can look and see which roles have replication privileges by
> checking the output of \du in psql, but there is nothing tying any
> roles to any specific slots.
i assume that a replication slot can only be used by 1 subscriber,
and subscribers can migrate; just to be clear the conneinfo is only
kept on the subscriber and used on the publisher, but not stored on the
publisher (unless active)
so if a replication slot is inactive, you can't contact for example the
user that (implicitely) created the replication slot, to see if it is
still needed for example.
background: i'm trying out an atypical? setup with many students
subscribing to a single publication server, thus with subscribers that
are not always online. As the number of slots might quickly grow:)
>
--
mvg,
Wim Bertels
--
Swerve me? The path to my fixed purpose is laid with iron rails,
whereon my soul is grooved to run. Over unsounded gorges, through
the rifled hearts of mountains, under torrents' beds, unerringly I rush!
-- Captain Ahab, "Moby Dick"
From | Date | Subject | |
---|---|---|---|
Next Message | Keith Fiske | 2020-05-14 13:02:53 | Re: viewing connectioninfo used by subscriber on the publication server when inactive |
Previous Message | Keith Fiske | 2020-05-14 12:05:23 | Re: viewing connectioninfo used by subscriber on the publication server when inactive |