Re: Inval reliability, especially for inplace updates
| От | Noah Misch |
|---|---|
| Тема | Re: Inval reliability, especially for inplace updates |
| Дата | |
| Msg-id | 20241031013924.cd.nmisch@google.com обсуждение исходный текст |
| Ответ на | Re: Inval reliability, especially for inplace updates (Nitin Motiani <nitinmotiani@google.com>) |
| Список | 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@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. I had pushed this during the indicated week, before your mail. Reverting it is an option. Let's see if more opinions arrive.
В списке pgsql-hackers по дате отправления: