Connector getting Inactive due to replication slot PID already exists

website start_replication slot slot => 'myreplslot' , on_message => sub { my Issues the START_REPLICATION SLOT command and immediately returns start replication slot postgres slot=pg2 11:04: CET ERROR: replication slot pg2 does not exist pg_basebackup: could not send replication command START_REPLICATION

start_replication slot START_REPLICATION SLOT “timescaledb_1” 5299D000000 TIMELINE 50 20:42:15 UTC ,app  START_REPLICATION SLOT stolon_7063fb99 16AB000000 TIMELINE 1 T20:27:57Z appkeeper  A replication slot ensures that the publisher will retain the WAL logs that are needed by the replicas even when they are disconnected from the

Share

Share

Link

Turn off sharing Copy link

See all details