From b77d903a808dae90e0108434bd5b8e8d1d2d820f Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Tue, 2 Jun 2026 13:14:26 +0000 Subject: [PATCH 1/2] docs: fix style inconsistencies in PSYNC_S1146 error description --- debugging/error-codes.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/debugging/error-codes.mdx b/debugging/error-codes.mdx index dfb34850..c273ae39 100644 --- a/debugging/error-codes.mdx +++ b/debugging/error-codes.mdx @@ -150,11 +150,11 @@ This reference documents PowerSync error codes organized by component, with trou - **PSYNC_S1146**: Replication slot invalidated. - The replication slot was invalidated by PostgreSQL, typically because WAL retention exceeded `max_slot_wal_keep_size` during a long-running snapshot. Increase `max_slot_wal_keep_size` on the source database, then either redeploy your Sync Config or delete the existing replication slot to recover. PowerSync will create a new slot and restart replication automatically. + PostgreSQL invalidated the replication slot, typically because WAL retention exceeded `max_slot_wal_keep_size` during a long-running snapshot. To recover, increase `max_slot_wal_keep_size` on the source database, then either redeploy your Sync Config or delete the existing replication slot. PowerSync creates a new slot and restarts replication automatically. -Other causes: `rows_removed` (catalog rows needed by the slot were removed), `wal_level_insufficient`, or `idle_timeout`. - -`idle_timeout` is a PostgreSQL 18+ slot invalidation, in this case increase `idle_replication_slot_timeout` instead of `max_slot_wal_keep_size`. + Other causes: `rows_removed` (catalog rows needed by the slot were removed), `wal_level_insufficient`, or `idle_timeout`. + + `idle_timeout` is a PostgreSQL 18+ slot invalidation. In this case, increase `idle_replication_slot_timeout` instead of `max_slot_wal_keep_size`. See [Managing and Monitoring Replication Lag](/maintenance-ops/production-readiness-guide#managing-and-monitoring-replication-lag) for guidance on sizing `max_slot_wal_keep_size`. From 9d2c206dcd2a650588fc826bbeab73546715f56c Mon Sep 17 00:00:00 2001 From: benitav Date: Wed, 3 Jun 2026 09:48:34 +0200 Subject: [PATCH 2/2] Apply suggestion from @benitav --- debugging/error-codes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debugging/error-codes.mdx b/debugging/error-codes.mdx index c273ae39..c6016c4d 100644 --- a/debugging/error-codes.mdx +++ b/debugging/error-codes.mdx @@ -150,7 +150,7 @@ This reference documents PowerSync error codes organized by component, with trou - **PSYNC_S1146**: Replication slot invalidated. - PostgreSQL invalidated the replication slot, typically because WAL retention exceeded `max_slot_wal_keep_size` during a long-running snapshot. To recover, increase `max_slot_wal_keep_size` on the source database, then either redeploy your Sync Config or delete the existing replication slot. PowerSync creates a new slot and restarts replication automatically. + Postgres invalidated the replication slot, typically because WAL retention exceeded `max_slot_wal_keep_size` during a long-running snapshot. To recover, increase `max_slot_wal_keep_size` on the source database, then either redeploy your Sync Config or delete the existing replication slot. PowerSync creates a new slot and restarts replication automatically. Other causes: `rows_removed` (catalog rows needed by the slot were removed), `wal_level_insufficient`, or `idle_timeout`.