| From: | Nitin Motiani <nitinmotiani(at)google(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(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-28 08:57:03 |
| Message-ID: | CAH5HC97fbvr63wJO23k6N0YmQh8BK3QE8ch3cQC=dWJJBxaCjw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Thanks
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2024-10-28 08:59:35 | Re: sslinfo extension - add notbefore and notafter timestamps |
| Previous Message | Andrei Lepikhov | 2024-10-28 08:51:02 | Re: Add ExprState hashing for GROUP BY and hashed SubPlans |