Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o3MpR-0000JU-VV for pgsql-admin@arkaria.postgresql.org; Mon, 20 Jun 2022 19:12:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o3MpQ-0001nq-OL for pgsql-admin@arkaria.postgresql.org; Mon, 20 Jun 2022 19:12:52 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o3MpQ-0001ng-C9 for pgsql-admin@lists.postgresql.org; Mon, 20 Jun 2022 19:12:52 +0000 Received: from mail-pg1-x52d.google.com ([2607:f8b0:4864:20::52d]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1o3MpO-0004ew-3I for pgsql-admin@lists.postgresql.org; Mon, 20 Jun 2022 19:12:51 +0000 Received: by mail-pg1-x52d.google.com with SMTP id r66so5101613pgr.2 for ; Mon, 20 Jun 2022 12:12:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:from:mime-version:date:subject:message-id :to; bh=fLi9G6Ug63mvPml026fmgp0wcJL/L7DuK0wRXbKBgv8=; b=D5UNeEKqpVWv/+u7sjD4wNFRGTygV7KLUhwAdyoN6VIqPcIRHEFfLo+eK0aLvDyURO JPJWmfYgnlio/N4PU5NnBH9Zz5g/9kUNaq0iVIVZJLllutq1rV4yKw05QjR10iCgFUMz lwZwNLJk2fmyJemh2UD+ujvvOSpLmvNTnljyAv3Q6TsnMXHIeRycnb312WXvnabm3zKy shCZKiRK1U5HlIcqbBwz9N/jDdKNE23jE9zOlBxidqQjiNqE2ZJS5elQgNd8hpCEraIm qKaVK8kZGvj/yZYUWJxntvAQZoFNnzvzZvRHDwnirTaoIKRAhsZ8GnKgI0ZAbuGTDCfc uHxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:content-transfer-encoding:from:mime-version:date :subject:message-id:to; bh=fLi9G6Ug63mvPml026fmgp0wcJL/L7DuK0wRXbKBgv8=; b=uvxl1vkq0B5IOvtIESBV5fcHjZZsMBpPalHNEzA5+aCp0lk00AT0F6lAI86mk3bV5G kMvR38gwh/A04uHhIud3tyavqQNslt4Ke5rep6y0BfXBYw5qyxtcfjYalV80Vq9LHXsy 6bRbSmCuocjXq9KqtKjjrD0DtyK1CqC7d1qs7/25adtBJ5RzsPrJkPTo+ilk04Zfakbg lSI0fG2Y0+vGd+KkUp+hp6JLGJTE5nf5xZA7NTf0dIV/jWwkgWFbctRsP8+dV5gi7Ug/ mUgG8NVIyzkUuWSfvn2UFtRN0lMpKUpgtWW3JvfJ1mypvfctwlLkWxYi1IXLkShagr8Q mrYA== X-Gm-Message-State: AJIora9WpqyihYg6RzVoYBjU9JbG9SASwXh680ztO385/yh8dzCKrkKX rUtOvzevkfR4Mj6sySMR/xVh7W+PM/Q= X-Google-Smtp-Source: AGRyM1thgRDQTuCa/GL/gNdPcu04ejVFJEB8epGFSoLuWYnOaiSkvniHUG/C8omjz7AN6SqI6ZP3Iw== X-Received: by 2002:a05:6a00:1894:b0:522:d414:61f7 with SMTP id x20-20020a056a00189400b00522d41461f7mr26308573pfh.18.1655752368635; Mon, 20 Jun 2022 12:12:48 -0700 (PDT) Received: from smtpclient.apple (2603-8001-3e43-3464-6403-da7c-0bfc-4d5b.res6.spectrum.com. [2603:8001:3e43:3464:6403:da7c:bfc:4d5b]) by smtp.gmail.com with ESMTPSA id v16-20020a17090331d000b00168b4b550f2sm9083833ple.54.2022.06.20.12.12.48 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 20 Jun 2022 12:12:48 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Teja Jakkidi Mime-Version: 1.0 (1.0) Date: Mon, 20 Jun 2022 12:12:47 -0700 Subject: Inactive replication slots Message-Id: To: pgsql-admin@lists.postgresql.org X-Mailer: iPhone Mail (19A404) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello Everyone, I have a primary Postgres server with 2 standbys setup using streaming repli= cation. Both the stand by servers are using the replication slots. Today, when I checked the status of replication slots on primary, they are s= howing active=3D =E2=80=98f=E2=80=99. The data is replicating with no issues= but when the slots are inactive I know that the wal files generated after t= he restart_lsn will not be deleted and retains the transactions, which is ve= ry critical. I am not sure exactly why the slots are inactive and if there is a way to ac= tivate them back? I tried restarting both primary and standby but sis not have any effect.=20 Thanks and Regards, J. Teja Sri.=