Horton

Re: Online checksums patch - once again

Bruce Momjian <bruce@momjian.us>

View thread View on postgr.es
From: Bruce Momjian <bruce@momjian.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Magnus Hagander <magnus@hagander.net>, Heikki Linnakangas <hlinnaka@iki.fi>, Michael Banck <michael.banck@credativ.de>, Justin Pryzby <pryzby@telsasoft.com>, Robert Haas <robertmhaas@gmail.com>, Michael Paquier <michael@paquier.xyz>, Andres Freund <andres@anarazel.de>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2021-03-09T18:12:06Z
Lists: pgsql-hackers 
On Mon, Feb 15, 2021 at 02:02:02PM +0100, Daniel Gustafsson wrote:
> > On 11 Feb 2021, at 14:10, Bruce Momjian <bruce@momjian.us> wrote:
> > I don't think anyone has done anything wrong --- rather, it is what we
> > are _trying_ to do that is complex.
> 
> Global state changes in a cluster are complicated, and are unlikely to never
> not be.  By writing patches to attempts such state changes we can see which
> pieces of infrastructure we're lacking to reduce complexity.  A good example is
> the ProcSignalBarrier work that Andres and Robert did, inspired in part by this
> patch IIUC.  The more we do, the more we learn.

Do we support or document the ability to create a standby with checksums
from a primary without it, and is that a better approach?

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee

Commits

  1. Online enabling and disabling of data checksums

  2. Add documentation chapter about checksums

  3. Record data_checksum_version in control file.