Replication slot creation fails when name contains a dash · Issue #275

This also means that the pg_wal directory may run out of space Imagine a scenario where the replica fails forever and cannot be recovered (an

Replication slot creation fails when name contains a dash · Issue #275 A PostgreSQL replication slot may be stuck due to one of the following reasons: Check if the bgwriter process is healthy by inspecting its

This also means that the pg_wal directory may run out of space Imagine a scenario where the replica fails forever and cannot be recovered (an

rocket reels slot This slot has been set up automatically when creating a replica on Unfortunately, it failed with a permission error when I tried to invoke it

If the subscriber is unable to handle the message (for A shard message must be sent to a node that owns the slot the shard channel is hashed to

creation of replication slot failed Leaving a logical replication slot inactive prevents the vacuum from removing obsolete tuples from tables, so we recommend that you monitor replication slots

When using asynchronous replication a failover can cause lost transactions Worst case failover time for primary failure is: loop_wait + primary_start_timeout +