Re: Inval reliability, especially for inplace updates - Mailing list pgsql-hackers

From Nitin Motiani
Subject Re: Inval reliability, especially for inplace updates
Date
Msg-id CAH5HC97fbvr63wJO23k6N0YmQh8BK3QE8ch3cQC=dWJJBxaCjw@mail.gmail.com
Whole thread Raw
In response to Re: Inval reliability, especially for inplace updates  (Noah Misch <noah@leadboat.com>)
Responses Re: Inval reliability, especially for inplace updates
List pgsql-hackers
On Thu, Oct 24, 2024 at 8:24 AM Noah Misch <noah@leadboat.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.

Thanks



pgsql-hackers by date:

Previous
From: Andrei Lepikhov
Date:
Subject: Re: Add ExprState hashing for GROUP BY and hashed SubPlans
Next
From: Alexander Lakhin
Date:
Subject: Re: Better error reporting from extension scripts (Was: Extend ALTER OPERATOR)