How CloudNativePG manages physical replication slots for

replication slot does not exist   Dan replication slot is active for pid

does not exist If it already exists, it must be empty -S slotname --slot=slotname This option can only be used together with -X stream

The CREATE SUBSCRIPTION command would create the replication slot There must be something in your setup that you are not telling us  Hi, I set up logical replication a few days ago, but it's throwing some weird log lines that have me worried Does anybody have experience

panda spin 88 slot The replication slot basically tells Postgres not to recycle or remove any WAL files that could ultimately prevent it from catching up with the The slot to be dropped must be inactive before it can be removed It is not possible to forcibly drop an active replication slot Change history PostgreSQL