Re: Offline enabling/disabling of data checksums
От | Fabien COELHO |
---|---|
Тема | Re: Offline enabling/disabling of data checksums |
Дата | |
Msg-id | alpine.DEB.2.21.1903261235240.20796@lancre обсуждение исходный текст |
Ответ на | Re: Offline enabling/disabling of data checksums (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: Offline enabling/disabling of data checksums
|
Список | pgsql-hackers |
Bonjour Michaël, >> Here is an attempt at improving the Notes. [...] > > So, the ordering of the notes for each paragraph is as follows: 1) > Replication issues when mixing different checksum setups across nodes. > 2) Consistency of the operations if killed. 3) Don't start Postgres > while the operation runs. > > Your proposal is to switch the order of the paragraphs to 3), 1) and > then 2). Yes. I suggest to emphasize cluster corruption risks by putting them first. > Do others have any opinion? I am fine with the current > order of things, still it may make sense to tweaks the docs. > > In the paragraph related to replication, the second statement is > switched to be first so as the docs warn first, and then give > recommendations. Yep. > This part makes sense. Yep! > I am not sure that "checksum status" is a correct term. It seems to > me that "same configuration for data checksums as before the tool ran" > or something like that would be more correct. Possibly, I cannot say. -- Fabien.
В списке pgsql-hackers по дате отправления: