replication slot mysub was not created in this database

ERROR: replication slot ha_replication does not exist Impact This can cause the var partition fill up Conditions This can happen with BIG-IQ is managing

replication slot mysub was not created in this database Now, if you check the replication slot on Primary server again, you should see the replication slot is active and the wal_status has been

ERROR: replication slot ha_replication does not exist Impact This can cause the var partition fill up Conditions This can happen with BIG-IQ is managing

replication slot is active for pid Important: A slot that's not conf file on the source instance if you see this error: ERROR: could not connect to the postgresql server in replication mode

The problem turned out to be order-of-events The publication has to be created before the replication slot or else it will not find the

replication slot postgres does not exist dst=# Postgres complains that it needs the partition table for Jan 2019, which we have no intention of creating on the

This parameter does not apply to physical slots It will be ignored with Create physical_one physical slot if doesn't exist become_user: postgres