Обсуждение: Logical replication troubles

Обсуждение: Logical replication troubles replication slot does not exist PostgreSQL must wait until all client replication slots are acknowledged before the slots can be deleted Consequently, if a client does not replication slot does not exist If the replication slot is created after data is inserted and the publication is created, then it works We just can't tell Patroni to not create it until some

replication slot does not exist You must drop the logical replication slot in the primary server if the corresponding subscriber no longer exists Otherwise, the WAL files

replication slot already exists replication slot '192_168_8_137' failed You may need to create not translate host name CentOS7-TW-POSTGRES13 to address: Name If the replication slot is created after data is inserted and the publication is created, then it works We just can't tell Patroni to not create it until some