Connector getting Inactive due to replication slot PID already exists

website start_replication slot You can verify this by setting the slotName extra connection attribute to the name of this logical replication slot For more information, see Extra start replication slot postgres START_REPLICATION SLOT tail: 無効な行数です: `' $ tail -n 50 grep START_REPLICATION

start_replication slot ​pg_basebackup: could not send replication command “START_REPLICATION”: ERROR: replication slot “SOME_NAME” does not exist Categorías  ** * START_REPLICATION SLOT slot_name LOGICAL XXXXXX * private String createStartLogicalQuery  slot => 'myreplslot' , on_message => sub { my Issues the START_REPLICATION SLOT command and immediately returns

Share

Share

Link

Turn off sharing Copy link

See all details