Re: pgsql: Online enabling and disabling of data checksums - Mailing list pgsql-committers

From Aleksander Alekseev
Subject Re: pgsql: Online enabling and disabling of data checksums
Date
Msg-id CAJ7c6TPRTnQFXXX1CRcYoTLXw2swtDH==uSz1MYoMKdLrKZHjA@mail.gmail.com
Whole thread Raw
In response to pgsql: Online enabling and disabling of data checksums  (Daniel Gustafsson <dgustafsson@postgresql.org>)
Responses Re: pgsql: Online enabling and disabling of data checksums
List pgsql-committers
Hi Daniel,

> Online enabling and disabling of data checksums
>
> [...]

I noticed a little mistake:

```
/*
 * Await state transition to "on" in all backends. When done we know that
 * data data checksums are both written and verified in all backends.
 */
```

The word "data" is repeated twice.

Also there are inconsistencies in the way
XLogCtlData->data_checksum_version,
ControlFileData->data_checksum_version and certain variables are
assigned. Sometimes a hardcoded 0 is used and sometimes
PG_DATA_CHECKSUM_OFF. I suggest using values of the enum
ChecksumStateType for readability / consistency.

Here are corresponding patches.

--
Best regards,
Aleksander Alekseev

Attachment

pgsql-committers by date:

Previous
From: Fujii Masao
Date:
Subject: pgsql: Release postmaster working memory context in slotsync worker
Next
From: Fujii Masao
Date:
Subject: pgsql: Add TAP tests for log_lock_waits