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 1t6K9u-00CA1L-DE for pgsql-hackers@arkaria.postgresql.org; Thu, 31 Oct 2024 01:39:34 +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 1t6K9s-00ENZq-0z for pgsql-hackers@arkaria.postgresql.org; Thu, 31 Oct 2024 01:39:32 +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 1t6K9r-00ENZi-Fx for pgsql-hackers@lists.postgresql.org; Thu, 31 Oct 2024 01:39:32 +0000 Received: from mail-ot1-x32a.google.com ([2607:f8b0:4864:20::32a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t6K9p-003unp-Ag for pgsql-hackers@postgresql.org; Thu, 31 Oct 2024 01:39:31 +0000 Received: by mail-ot1-x32a.google.com with SMTP id 46e09a7af769-718998df806so197833a34.1 for ; Wed, 30 Oct 2024 18:39:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1730338767; x=1730943567; darn=postgresql.org; h=user-agent: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=JKvfPMJH7Pd0U/W9cJs/dEuukCfFtwsImyKJl57jm6w=; b=W1ZbB3C7gxw3Up0y64F0VDxSbVPlQwnNpZz+IDyIQ9xgi1HboGeuVW3Jy9pkjUHPUu H1wMG4ALwSBspiatyfPj0vwswf0Hn1R910LgsgVvduxlLH1MpSS+BY1IboOT61VO+xQ+ rtm1iXrolzeKeIz941vaF+YHmPRsZzXJm7w8c= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730338767; x=1730943567; h=user-agent: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=JKvfPMJH7Pd0U/W9cJs/dEuukCfFtwsImyKJl57jm6w=; b=k02Tg4MEupTb3ikau4I52NLuQ1jBEJdjWrHACxJBz0PvjMUHgORGyyPePACFcoVzYH 3xo2sSiDUNkWUKNp8MpdLlzCV48Ga1I4gFfV+fzqTXu+KL64dDoP3u8JyhI9EawQNMl8 tYMJ5XTLkyB5KCQfTZdHxmqlS10ucdS/RnWvMuFIpgaZj3KQdzV9S9mIjjgxXiGGg99R gE/c2spxqeNTwHN3WCCXFsL84TGjlCg+o8w0wnFAiW80fmdsWclMh5I6CIxAhPwYugih V/syeglSYHQkpGSaMl+71GJGW3S88EJma2UuM7vukvPHBd+r1J/suUVCx7fJSojI+SMi VnKA== X-Forwarded-Encrypted: i=1; AJvYcCW840lQwc8GQdtxGizaFS01LTqB5KP/NTh9O3nML9HKZCOKArIVbW5jS5MMFnYlg9C5qEnArv+uYRabd9iB@postgresql.org X-Gm-Message-State: AOJu0YxKvzv+o6GNiqsSDQBARFbARugFzn5OfDXt8AWeLrG+NNanQGbF TCYrKKLXm5i8Sjm25Kr81+Cu3aHyYiulw7AehfJsYDTfRoBuUlMTwXVY2s3B7g== X-Google-Smtp-Source: AGHT+IHF2AbMq+bPknS/W/NKwVWE4w/C1ULssZQ3qlL3PAmh50Rvow0bkWNE2AP7oWoinshOFWnN/A== X-Received: by 2002:a05:6870:2105:b0:278:1f2:a23f with SMTP id 586e51a60fabf-29051b7d36emr15274927fac.13.1730338767090; Wed, 30 Oct 2024 18:39:27 -0700 (PDT) Received: from google.com ([2600:1702:a20:5750::48]) by smtp.gmail.com with ESMTPSA id 586e51a60fabf-294874d6687sm224287fac.31.2024.10.30.18.39.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Oct 2024 18:39:26 -0700 (PDT) Date: Wed, 30 Oct 2024 18:39:24 -0700 From: Noah Misch To: Nitin Motiani Cc: Andres Freund , pgsql-hackers@postgresql.org Subject: Re: Inval reliability, especially for inplace updates Message-ID: <20241031013924.cd.nmisch@google.com> References: <20240618015730.jijhox2a3w3t26en@awork3.anarazel.de> <20240618152349.7f.nmisch@google.com> <20240831010711.67.nmisch@google.com> <20240930193350.04.nmisch@google.com> <20241013004511.9c.nmisch@google.com> <20241024025357.a8.nmisch@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit 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, Oct 28, 2024 at 02:27:03PM +0530, Nitin Motiani wrote: > On Thu, Oct 24, 2024 at 8:24 AM Noah Misch wrote: > > With the releases wrapping in 2.5 weeks, I'm ambivalent about pushing this > > before the release or after. Pushing before means fewer occurrences of > > corruption, but pushing after gives more bake time to discover these changes > > were defective. It's hard to predict which helps users more, on a > > risk-adjusted basis. I'm leaning toward pushing this week. Opinions? > > I lean towards pushing after the release. This is based on my > assumption that since this bug has been around for a while, it is > (probably) not hit often. And a few weeks delay is better than > introducing a new defect. I had pushed this during the indicated week, before your mail. Reverting it is an option. Let's see if more opinions arrive.