Re: Online enabling of checksums
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Magnus Hagander <magnus@hagander.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Daniel Gustafsson <daniel@yesql.se>
Date: 2018-02-22T19:24:37Z
Lists: pgsql-hackers
On 2018-02-22 08:22:48 -0500, Peter Eisentraut wrote: > On 2/21/18 15:53, Magnus Hagander wrote: > > *Two new functions are added, pg_enable_data_checksums() and > > pg_disable_data_checksums(). The disable one is easy -- it just changes > > to disable. The enable one will change the state to inprogress, and then > > start a background worker (the “checksumhelper launcher”). This worker > > in turn will start one sub-worker (“checksumhelper worker”) in each > > database (currently all done sequentially).* > > This is at least the fourth version of the pattern launcher plus worker > background workers. I wonder whether we can do something to make this > easier and less repetitive. Not in this patch, of course. I suspect I'm going to get some grief for this, but I think the time has come to bite the bullet and support changing databases in the same process... 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