Using PostgreSQL Logical Replication to Maintain an Always Up-to

error It is strange, because due to replication slots it shouldn't be happening On master there is replication slot for slave and it shows

Using PostgreSQL Logical Replication to Maintain an Always Up-to Postgres prevents active slots from being dropped If it does happen , PowerSync would

error It is strange, because due to replication slots it shouldn't be happening On master there is replication slot for slave and it shows

electric dreams slot car Previous PostgreSQL logs shows usage of the replication slot with 2 different PIDs with a delay between the 2 calls of less than a minute

Now a common cause for this kind of issue are replication slots which are not advanced: in that case, Postgres will hold on to all WAL segments

error_ replication slot is active for pid When replication slots is enabled, you might end up running out of disk space due to PostgreSQL trying to retain WAL files requested by a replication slot

Examples Advancing a physical replication slot: postgres=# SELECT slot_name, slot_type, active, restart_lsn, confirmed_flush_lsn FROM pg_replication_slotsgx