On 2020-05-25 10:19, Anders Bøgh Bruun wrote:
> Thank you for that clarification. It helps me understand how things work
> a lot better.
> I know this might be a bit off topic, but my challenge here is that we
> are using Patroni (by using Zalando's postgres-operator for Kubernetes),
> and any replication slot not created by Patroni, seems to be removed,
> whenever the master pod restarts. We therefore specify in the Patroni
> config, that a permanent replication slot should be created for our
> usage to do logical replication of some select tables, to our data
> warehouse. That means that the replication slot is created as soon as
> the database is ready to use, which is also before any tables, data or
> publications are created. Can you give me a hint as to what the correct
> way to set this up would be?
> Or do I need to try contacting the Patroni devs instead?
That would probably be best.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
