Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sq2Ml-006NkN-VS for pgsql-hackers@arkaria.postgresql.org; Mon, 16 Sep 2024 03:25:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sq2Mk-00ARqr-GQ for pgsql-hackers@arkaria.postgresql.org; Mon, 16 Sep 2024 03:25:30 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sq2Mk-00ARqi-56 for pgsql-hackers@lists.postgresql.org; Mon, 16 Sep 2024 03:25:30 +0000 Received: from mail-oi1-x233.google.com ([2607:f8b0:4864:20::233]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sq2Md-001Ngc-27 for pgsql-hackers@lists.postgresql.org; Mon, 16 Sep 2024 03:25:28 +0000 Received: by mail-oi1-x233.google.com with SMTP id 5614622812f47-3e03d17365bso2255543b6e.1 for ; Sun, 15 Sep 2024 20:25:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726457122; x=1727061922; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=toEiPy93pgP0qFnYK8eXCOn0TSbDPJczCK6w3Yk41Yk=; b=nlvd+q3diJp9tUC3O4j8ebOn3c33Cgmp+9KttJSMtdwJcyIJIu1a7Fx+BuvDBgtoXt Qy0rADrMxEKjktlz2vYc1b+wHPBHGsPQwtSpnFEwIKiS7ne9B2t26mdGPSVD4qpEIzCM +w59NDXAK5+oeBsdcXnnJNzwma0f20cHvm+iepML/ydQ2kBtBqgpqp5TkjQFtze3Ta2e omklpnC3+aGMWkZZ2MUs9goNgPfdr3O/QLS9tmm05Fj0qipD0n8HAQYwFdzi01dAenVf lpWslI2gxFyz5iurxq6jUB/0U8KMRZEwou20gCEKqAZxGFFKYHKJGzkgXGE9i+4gp3LS yqkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726457122; x=1727061922; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=toEiPy93pgP0qFnYK8eXCOn0TSbDPJczCK6w3Yk41Yk=; b=DI+jE3bwDkCNZD02ZN8jy0CS/qgLxLBtW0CryZLw3C/nTeane9ObrZA7LhbEcWU5jh HR97Dpr8jCXvcuOM0EdkW6GHJQCKoJI7AsmNRykqx5JauhpbxiMWTg4SHd9doJow+TEi bPW+DdjdgUrHMhL0Yf0h7KKzZXgs6LMIVmNrGlPvqd9swGW37a3ITxZ63trrHTH5uvCb OjsHfCKW7JpWDQK1cSHrT0pGiVnPqYdAdc+tvEFGTOJOtolQMSLXT9LwEPRSd4mnUywK ocZOFUPHmF1gHKyG1/uBWgrOwzCMnX6bZikQgJ0Ya2Pn3W1cMG0e3klj5v57i0Ji89RO uIWA== X-Forwarded-Encrypted: i=1; AJvYcCVpl5ReuDAwjsuNEcr/TuJ8/UsJWxpSJ19z73qL50+8vCXAwRIyPg00EK15ztqODmmeVZSEV9UeVRhUUPuU@lists.postgresql.org X-Gm-Message-State: AOJu0YzOSj7EJCAwj7bJBDFIaiVU1C9AnkXmMsxShPH+jIk7DzjwtnqG eTaDeRcNJ8vDu6O5lajZ7WyYUK5rvUm/UJTpanIGxjyW3Gr92QuqrAtZqFqvcQg/qruZA0faus3 GUiHoqVpRLCXnmAiufcGvg2jY4AQ= X-Google-Smtp-Source: AGHT+IGuzhX9+867susleHp9v25Keob2ZimeLMIlIDBXEHrN75GQBHTCXuthZnhZ2xMXp6F1sp7HOeK4D3wpDuL5Klg= X-Received: by 2002:a05:6808:3994:b0:3e0:3946:b92 with SMTP id 5614622812f47-3e071b28ccbmr7654586b6e.45.1726457122347; Sun, 15 Sep 2024 20:25:22 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Amit Kapila Date: Mon, 16 Sep 2024 08:55:10 +0530 Message-ID: Subject: Re: Introduce XID age and inactive timeout based replication slot invalidation To: Bharath Rupireddy Cc: shveta malik , Peter Smith , Ajin Cherian , Bertrand Drouvot , Masahiko Sawada , Nathan Bossart , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Sep 10, 2024 at 12:13=E2=80=AFAM Bharath Rupireddy wrote: > > On Mon, Sep 9, 2024 at 3:04=E2=80=AFPM Amit Kapila wrote: > > > > > > > > We should not allow the invalid replication slot to be altered > > > > > > irrespective of the reason unless there is any benefit. > > > > > > > > > > Okay, then I think we need to change the existing behaviour of th= e > > > > > other invalidation causes which still allow alter-slot. > > > > > > > > +1. Perhaps, track it in a separate thread? > > > > > > I think so. It does not come under the scope of this thread. > > > > It makes sense to me as well. But let's go ahead and get that sorted ou= t first. > > Moved the discussion to new thread - > https://www.postgresql.org/message-id/CALj2ACW4fSOMiKjQ3%3D2NVBMTZRTG8Ujg= 6jsK9z3EvOtvA4vzKQ%40mail.gmail.com. > Please have a look. > That is pushed now. Please send the rebased patch after addressing the pending comments. --=20 With Regards, Amit Kapila.