Re: Inval reliability, especially for inplace updates

From: Noah Misch <noah(at)leadboat(dot)com>
To: Nitin Motiani <nitinmotiani(at)google(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Inval reliability, especially for inplace updates
Date: 2024-10-31 01:39:24
Message-ID: 20241031013924.cd.nmisch@google.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 28, 2024 at 02:27:03PM +0530, Nitin Motiani wrote:
> On Thu, Oct 24, 2024 at 8:24 AM Noah Misch <noah(at)leadboat(dot)com> 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-10-31 02:10:09 Re: [PATCH] Add array_reverse() function
Previous Message Yushi Ogiwara 2024-10-31 01:22:11 Making error message more user-friendly with spaces in a URI