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 1rgtdT-008XHQ-Gn for pgsql-hackers@arkaria.postgresql.org; Sun, 03 Mar 2024 21:44:43 +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 1rgtdR-002Q6M-Ow for pgsql-hackers@arkaria.postgresql.org; Sun, 03 Mar 2024 21:44:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rgtdR-002Q6E-Fb for pgsql-hackers@lists.postgresql.org; Sun, 03 Mar 2024 21:44:41 +0000 Received: from mail-io1-xd29.google.com ([2607:f8b0:4864:20::d29]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rgtdO-002bzF-KW for pgsql-hackers@lists.postgresql.org; Sun, 03 Mar 2024 21:44:41 +0000 Received: by mail-io1-xd29.google.com with SMTP id ca18e2360f4ac-7c8387ca6ecso73550339f.0 for ; Sun, 03 Mar 2024 13:44:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709502276; x=1710107076; darn=lists.postgresql.org; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=YdhAqjzYq9tjniW2ysN3EFVpQZv+8F26DPdamHXVIJc=; b=MaKGS5QftiVbumagkvUiFEdTx7bqf0SNj9nKw37EialST1zokM+4xinpTe5IYHa2ZW yXUAQ5i1DDoi2Rwkn47e4VvrhhoSAT6wlPuurMIu6kfPYJf5J91gc3smZJyGElZruMd4 f/CLa8qccFz2vWBmr769LMnW6fAG5W4YvNlbXiwbDUbHda4BaNV2C3adeFW+aO+PEi2q JyepvKrmnGT9gwrt/VCasvb1d/v1b7LpTe7VJBqa5bjHy1k2qEjT5ZhELsfgmfryMQhj Qvgf2yalCWnr++GxFwDZxgKiPtUMB9tZMwNlntvsbnmzPzC/fLl/8JggvI5J6+KncRtC flGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709502276; x=1710107076; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=YdhAqjzYq9tjniW2ysN3EFVpQZv+8F26DPdamHXVIJc=; b=GJ5g7OP9Kx5AIpz2rIWimZLcJYGXuRTAiFeVPZtlGr7cEeOtOMRFnPFOZmt0lgObSx VUNclMx6nuPBu9nL85GAbHF2XSJPwZ/V8O88T4TOeoenpUkaRhGRrDOSXaXy51ENWWV1 cHb42E+yoWXX2CBaQnLkh6jvPbP7dqq+tEyWBaSQRPGCaAD/G0sy9hOoQelHhukUdobk WafpX4GzpHsCVSjo9/q6md+d+vFKlA3FigjJ7vjw11mkj9oQp8pNsd74inL6VPO5fCjG PTEo38rI8J/UFOrHifmuPPDhcsbiGUpnl5LtBNBYoYR/hygXWQu8GbC5mN+3KcEPTQPT 0VVQ== X-Forwarded-Encrypted: i=1; AJvYcCViLlgvueoFup5tQnq2PCXdGRIzdBQtAWDFvKI5/svCqnWsw1BPpRBZSdH6sVzq08ttRCfmpSX0+NLscTovLeN/SUkXVMkdlgG4KiQn/52qWkeh X-Gm-Message-State: AOJu0YxBJuqbP7nMrj8LyUtL3OU69SB0G71fOJIF58X+D6iOBG2765CU A5tm1pa9MEJquRZMOVj2CDM/d18myCrmpuGzDHghGNJgMwWJrdyN X-Google-Smtp-Source: AGHT+IG4BhMUB+53FgECY7VKFukahWqRO5KXbtZeYuIVLNAno5/u2YN73j0/4zAnduDflZqsZBhWdA== X-Received: by 2002:a05:6602:3705:b0:7c8:298:8c88 with SMTP id bh5-20020a056602370500b007c802988c88mr10403447iob.7.1709502276538; Sun, 03 Mar 2024 13:44:36 -0800 (PST) Received: from nathanxps13 (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id c19-20020a02a413000000b00472f79e0001sm1938834jal.171.2024.03.03.13.44.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 03 Mar 2024 13:44:36 -0800 (PST) Date: Sun, 3 Mar 2024 15:44:34 -0600 From: Nathan Bossart To: Bharath Rupireddy Cc: Bertrand Drouvot , PostgreSQL Hackers Subject: Re: Introduce XID age and inactive timeout based replication slot invalidation Message-ID: <20240303214434.GA3036597@nathanxps13> References: <20240301221108.GB3024365@nathanxps13> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sun, Mar 03, 2024 at 11:40:00PM +0530, Bharath Rupireddy wrote: > On Sat, Mar 2, 2024 at 3:41 AM Nathan Bossart wrote: >> Would you ever see "conflict" as false and "invalidation_reason" as >> non-null for a logical slot? > > No. Because both conflict and invalidation_reason are decided based on > the invalidation reason i.e. value of slot_contents.data.invalidated. > IOW, a logical slot that reports conflict as true must have been > invalidated. > > Do you have any thoughts on reverting 007693f and introducing > invalidation_reason? Unless I am misinterpreting some details, ISTM we could rename this column to invalidation_reason and use it for both logical and physical slots. I'm not seeing a strong need for another column. Perhaps I am missing something... -- Nathan Bossart Amazon Web Services: https://aws.amazon.com