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 1tB9mS-002Crt-L7 for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Nov 2024 09:35:19 +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 1tB9mQ-00Cplr-0L for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Nov 2024 09:35:18 +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 1tB9mP-00Cpli-Mt for pgsql-hackers@lists.postgresql.org; Wed, 13 Nov 2024 09:35:18 +0000 Received: from mail-lj1-x22a.google.com ([2a00:1450:4864:20::22a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tB9mN-001dz3-Qw for pgsql-hackers@lists.postgresql.org; Wed, 13 Nov 2024 09:35:17 +0000 Received: by mail-lj1-x22a.google.com with SMTP id 38308e7fff4ca-2fc968b3545so59128931fa.2 for ; Wed, 13 Nov 2024 01:35:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731490514; x=1732095314; 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=VG64LRAroq+6ZHJzAQJzh2HkFGGcmbg65nI1NIkFJ5g=; b=FTK+d/l283zu9ifdm9+AELmeOossy+umHlxhX4IItfNnFEJTgZRrXpljTZ+L7n28ZS pdM3bNLsVr4yRSE3ZjZmUEZFUFC4IEO2IZRwjxTpejOB4w9RgkgCtDOCzbNl4QBpRqK+ cdg5uOGkYYL14K8zDTygVv5l+SC4OZ70H4yvywZHf1o8otu6STsLsGKQFWC+/g7nEwFk vhsKibcLquUaADcg3asXFLnccH9qhgGhVbXl4ImCdlyUnzug9R5LKEVpXFbNVqK6RnlG DWNiwfKXE2pijGERDZQSo+IoVrqUhQLj93Z2GxRsdrnKG9a1Gqe/7z/pNL83cBUdpKrT /UsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731490514; x=1732095314; 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=VG64LRAroq+6ZHJzAQJzh2HkFGGcmbg65nI1NIkFJ5g=; b=dfuAZIO9Fw/MM2mbr33KhyJo8xTNu2/AXk4pPMfbjQSTqojzyvdlwfA7NGL50KpwDF l1CG3fCvZdsbaat8myS2HfHOVOfCEcRU64EEMTdNu0vTkYQjt1OYtKQ2iq+ilVJDVjK5 YJs2Y4bVM4JxyZD1YdwWFKGIPKzrkC6hGBz4xzrpgmj3CMZSGUGhi0SvTR9WYq2bKfQK ZfSpsH4i69+CuwPhH1S8B5H5RWIQKwKJZsih+fnS8v4jIpz6J2eLjq3orMKE38j2GqMP jTriOJ2S5sni/QcvfXeTeXMdiihZDrqOD47OPZK1VXtH4733RC49aI0I35AGWp2xRvEq rY9A== X-Forwarded-Encrypted: i=1; AJvYcCX74Hy56gengiS7PQf00MNDCVIlOq6JvmArVRs2oBpFbw4uvLqYAioFpEuYbeD5EiAXNrsHeNxZokkFhppB@lists.postgresql.org X-Gm-Message-State: AOJu0Yxm9WVxGunh3fdBQeh2MqEWLbB4OUCgrcoXVYVogAgTnrIxlaDZ XSnH5V03sAqW7Cv+DueXEGmBy9yoOzOLKEL31EGoAVyd39l5/uuCE+x/PC9JIjQ4OPk5a3MLNla kkiBBxKjPVUBO7mPYF2XbMf11OuTwLjwpnjZm X-Google-Smtp-Source: AGHT+IHrh+TvYV0fX/JVz+3yMEfxz0CsnNSP6podPZzjWY258yngAW4CzW3PNGz6ymB/xzOdm6MX68d77uBL0CsuU3Q= X-Received: by 2002:a2e:a994:0:b0:2fb:4b40:1e1c with SMTP id 38308e7fff4ca-2ff4c655fa7mr11130831fa.36.1731490513843; Wed, 13 Nov 2024 01:35:13 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Nisha Moond Date: Wed, 13 Nov 2024 15:05:01 +0530 Message-ID: Subject: Re: Introduce XID age and inactive timeout based replication slot invalidation To: shveta malik Cc: Bharath Rupireddy , Peter Smith , Amit Kapila , 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 Wed, Sep 18, 2024 at 12:22=E2=80=AFPM shveta malik wrote: > > On Mon, Sep 16, 2024 at 3:31=E2=80=AFPM Bharath Rupireddy > wrote: > > > > Hi, > > > > > > Please find the attached v46 patch having changes for the above review > > comments and your test review comments and Shveta's review comments. > > > > Thanks for addressing comments. > > Is there a reason that we don't support this invalidation on hot > standby for non-synced slots? Shouldn't we support this time-based > invalidation there too just like other invalidations? > I don=E2=80=99t see any reason to *not* support this invalidation on hot standby for non-synced slots. Therefore, I=E2=80=99ve added the same in v48= . -- Thanks, Nisha