Re: Online enabling of checksums
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: pgsql-hackers@lists.postgresql.org,Magnus Hagander <magnus@hagander.net>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>,Tomas Vondra
<tomas.vondra@2ndquadrant.com>,Heikki Linnakangas <hlinnaka@iki.fi>,Daniel
Gustafsson <daniel@yesql.se>,Michael Banck <michael.banck@credativ.de>,Robert
Haas <robertmhaas@gmail.com>,Greg Stark
<stark@mit.edu>,PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2018-04-05T20:27:43Z
Lists: pgsql-hackers
On April 5, 2018 1:20:52 PM PDT, Magnus Hagander <magnus@hagander.net> wrote: >On Thu, Apr 5, 2018 at 10:14 PM, Andres Freund <andres@anarazel.de> >wrote: > >And even worse, without even announcing an intent to commit and giving >> people a chance to object. >> > >At least this patch was posted on the lists before commit, unlike many >others from many different people. And AFAIK there has never been such >a >rule. The more debatable a decision is, the more important it IMO becomes to give people a chance to object. Don't think there needs to be a hard rule to always announce an intent to commit. Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Commits
-
Online enabling and disabling of data checksums
- f19c0eccae96 19 (unreleased) landed
-
Deactive flapping checksum isolation tests.
- bf75fe47e444 11.0 landed
-
Add support for coordinating record typmods among parallel workers.
- cc5f81366c36 11.0 cited