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 1rwTJG-0020u7-A8 for pgsql-bugs@arkaria.postgresql.org; Mon, 15 Apr 2024 20:52:14 +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 1rwTJE-00FnBG-Kr for pgsql-bugs@arkaria.postgresql.org; Mon, 15 Apr 2024 20:52:12 +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 1rwTJE-00FnB8-1B for pgsql-bugs@lists.postgresql.org; Mon, 15 Apr 2024 20:52:12 +0000 Received: from mail-ot1-x333.google.com ([2607:f8b0:4864:20::333]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rwTJA-0031YZ-14 for pgsql-bugs@lists.postgresql.org; Mon, 15 Apr 2024 20:52:10 +0000 Received: by mail-ot1-x333.google.com with SMTP id 46e09a7af769-6ea0db2727bso2077078a34.2 for ; Mon, 15 Apr 2024 13:52:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1713214327; x=1713819127; darn=lists.postgresql.org; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=KJnPygQBTk86lFNVW15Qy/oLobMcgb8N6AyEn0uvZ/I=; b=VQNWyij+63B1da8DtNPWFgHOuYF/ITPwtuuD9OwKf2E9axFBgV1jVZzSszFnAtJSrQ WbDMCg67azVhlTSktsgPqI/FZFnm35o0D4UWq71m/E2DEmmlUb+jOmtb+gdNipEKWUM+ ZJcGal10NPaR0niAIPCMNMCpO4kifcs3idKQk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713214327; x=1713819127; h=user-agent:in-reply-to: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=KJnPygQBTk86lFNVW15Qy/oLobMcgb8N6AyEn0uvZ/I=; b=qIZk7WsYztKDk6P+urSOIB3I06Ez4qr4SuJT0aCZoveFmCXtL643f1DYY0/dp9T1DH zAhz9FyVDctYOnikqwwxcWSCXNn6jGavtr5vp9XkqTlEoX25HIpLwRe/BZBpx9oKeLUl DjSLozL9Uj7F3DAv1hhyEVGSb1HM8h0IReixWHy6ii8rTtv3tysXHBtVySBpdTd3AA3z kIPMuqaD7bADrxVPTI1UATg6p39Hlj2h/qq7cKd0rPtkqTCqZBuLMCh+ns5LIZqfGXQI ztb6JUV333YkpEVws9o43v/ETRZz7YZjDl6gTAVjsjP721UUmkvUXKoOW/6R05p3wq3C w4fw== X-Forwarded-Encrypted: i=1; AJvYcCXBEFQMCkR/unEb9ASria7z8Arbijsaji46xummiYxp1Btp/R99MvsG+7cGN1IvAPTjkBPQ2+Mr/hJ85PhdN/8a9OhsPqlv3GU5Xjo4kS68 X-Gm-Message-State: AOJu0Yy1Uig+eJMBQX15o/jqJ3wnQvLBoGlB3L63m15p2zWMBSMDzMy8 DP1q1bP+aM/Gof3WYAvGjXuVRQe1121l4vPSXZHMlrWRGPEOPW6lexaEk04P4A== X-Google-Smtp-Source: AGHT+IHv/nIup8XyNslflS8e5ZjqVnrpYnfowBHlkeEUg1BSRW9ygmzqqtEE7UQ/m6GLZMBkP369NQ== X-Received: by 2002:a9d:6c16:0:b0:6eb:8d20:3f1c with SMTP id f22-20020a9d6c16000000b006eb8d203f1cmr988302otq.37.1713214327288; Mon, 15 Apr 2024 13:52:07 -0700 (PDT) Received: from google.com ([2600:1702:a20:5750::48]) by smtp.gmail.com with ESMTPSA id m4-20020a0568301e6400b006eb79a40959sm805353otr.11.2024.04.15.13.52.06 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Apr 2024 13:52:06 -0700 (PDT) Date: Mon, 15 Apr 2024 13:52:04 -0700 From: Noah Misch To: Robert Haas Cc: Melanie Plageman , Matthias van de Meent , Peter Geoghegan , Alexander Lakhin , PostgreSQL mailing lists , Andres Freund Subject: Re: relfrozenxid may disagree with row XIDs after 1ccc1e05ae Message-ID: <20240415205204.57.nmisch@google.com> References: <20240304000717.1e@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.12 (2023-09-09) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Apr 15, 2024 at 12:35:59PM -0400, Robert Haas wrote: > I propose to remove this open item from > https://wiki.postgresql.org/wiki/PostgreSQL_17_Open_Items > > On the original thread (BUG #17257), Alexander Lakhin says that he > can't reproduce this after dad1539ae/18b87b201. Based on my analysis I have observed the infinite loop in production with v15.5, so that non-reproduce outcome is a limitation in the test procedure. (v14.2 added those two commits.) > of the code, I suspect that there is a residual bug, or at least that > there was one prior to 6f47f6883151366c031cd6fd4011e66d2c702a90. Can you say more about how 6f47f6883151366c031cd6fd4011e66d2c702a90 mitigated the regression that 1ccc1e05ae introduced? Thanks for discovering that.