Re: Online enabling of checksums
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Magnus Hagander <magnus@hagander.net>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>, Daniel Gustafsson <daniel@yesql.se>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Michael Banck <michael.banck@credativ.de>
Date: 2018-03-02T07:44:30Z
Lists: pgsql-hackers
On 2018-03-01 16:18:48 +0100, Magnus Hagander wrote: > On Thu, Mar 1, 2018 at 9:04 AM, Andres Freund <andres@anarazel.de> wrote: > > > On 2018-03-01 12:56:35 +0500, Andrey Borodin wrote: > > > I've tried to rebase this patch to 10 and, despite minor rebase issues > > (oids, bgw_type, changes to specscanner), patch works fine. > > > Do we provide backporting for such features? > > > > Definitely not. With very rare exceptions (OS compatibility and the > > like), features aren't backported. > > > > Yeah. And definitely not something that both changes the format of > pg_control (by adding new possible values to the checksum field) *and* adds > a new WAL record type... And even more so, I'm not even sure it makes sense to try to get this into v11. This is a medium-large complicated feature, submitted to the last CF for v11. That's pretty late. Now, Magnus is a committer, but nevertheless... Greetings, Andres Freund
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