Alexey Kondratov 6059801943 Enable Postgres data checksums (neondatabase/cloud#536) ...

We need checksums to verify data integrity, when we read it from
untrusted place (e.g. local disk) or via untrusted communication channel
(e.g. network). At the same time, we trust pageserver <-> redo process
communication channel, as it is just a pipe.

Here we enable calculation of data checksums in the wal redo process and
when we extract FPI during WAL injestion. Compute node (Postgres) will
verify checksum of every page after receiving it back from pageserver.
So it is pretty similar to how vanilla Postgres checks them.

There are two other places where we should verify checksums to
detect data corruption earlier:
- when we receive WAL records from safekeepers (already implemented,
  see: WalStreamDecoder::poll_decode)
- when we write layer files to disk and read back in memory from local
  disk or S3

2022-07-07 19:44:47 +02:00

..

restore_from_wal_archive.sh

Rename 'zenith_admin' role to 'cloud_admin'

2022-05-30 11:11:01 +03:00

restore_from_wal.sh

Enable Postgres data checksums (neondatabase/cloud#536)

2022-07-07 19:44:47 +02:00