Re: find replication slots that "belong" to a publication

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Willy-Bas Loos <willybas(at)gmail(dot)com>, Justin <zzzzz(dot)graf(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: find replication slots that "belong" to a publication
Date: 2025-04-07 13:31:06
Message-ID: f673c080f33805fdf5e3060f8f3338ebc803eb19.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, 2025-04-07 at 12:16 +0200, Willy-Bas Loos wrote:
> My question is not so much about "can i drop a certain replication slot", 
> more about "does this publication still have any replication slots?".
> Or, if you will: "what's the publication for this replication slot?".
>
> I've double checked the views that you suggested, and I found that I can relate
> the WAL sender processes to replication slots through pg_replication_slots.active_pid .
> I've also looked into replication origins.
>
> But I can't find a link to the publication. And that's what I need to know.

I don't think that there is a connection between a publication and a
replication slot. That connection is only made when a subscriber connects
and runs the START_REPLICATION command [1] and specifies the "pgoutput"
plugin with the "publication_names" option [2].

I don't think you can see that information reflected in a system view
on the primary. You'd have to query "pg_subscription" on the standby.

Yours,
Laurenz Albe

[1]: https://www.postgresql.org/docs/current/protocol-replication.html#PROTOCOL-REPLICATION-START-REPLICATION-SLOT-LOGICAL
[2]: https://www.postgresql.org/docs/current/protocol-logical-replication.html#PROTOCOL-LOGICAL-REPLICATION-PARAMS

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Artur Zakirov 2025-04-07 14:05:59 Re: Performance regression when adding LIMIT 1 to a query
Previous Message Joe Conway 2025-04-07 13:21:34 Re: Kubernetes, cgroups v2 and OOM killer - how to avoid?