Re: Online enabling of checksums - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Online enabling of checksums
Date
Msg-id CABUevEz7qhM_ze0DchGW6-_7R0pvTZ3Y-tvUx2i1AETs+RU0HQ@mail.gmail.com
Whole thread Raw
In response to Re: Online enabling of checksums  (Andrey Borodin <x4mmm@yandex-team.ru>)
Responses Re: Online enabling of checksums  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Mon, Mar 19, 2018 at 11:40 AM, Andrey Borodin <x4mmm@yandex-team.ru> wrote:
Hi, Daniel!

> 19 марта 2018 г., в 4:01, Daniel Gustafsson <daniel@yesql.se> написал(а):
>
> Fixed in patch just posted in 84693D0C-772F-45C2-88A1-85B4983A5780@yesql.se
> (version 5). Thanks!


I've been hacking a bit in neighboring thread.
And come across one interesting thing. There was a patch on this CF on enabling checksums for SLRU. The thing is CLOG is not protected with checksums right now. But the bad thing about it is that there's no reserved place for checksums in SLRU.
And this conversion from page without checksum to page with checksum is quite impossible online.

If we commit online checksums before SLRU checksums, we will need very neat hacks if we decide to protect SLRU eventually.

What do you think about this problem?

One would be adjusted to work with the other, yes. It makes no sense to now allow online enabling once SLRU protection is in there, and it doesn't make sense for either of these patches to be blocking the other one for commit, though it would of course be best to get both included.


--

pgsql-hackers by date:

Previous
From: Arthur Zakirov
Date:
Subject: Re: [PROPOSAL] Shared Ispell dictionaries
Next
From: Amit Langote
Date:
Subject: Re: [HACKERS] Add support for tuple routing to foreign partitions