Re: Changing the state of data checksums in a running cluster
От | Bruce Momjian |
---|---|
Тема | Re: Changing the state of data checksums in a running cluster |
Дата | |
Msg-id | aKSklV1QwxMB1QCr@momjian.us обсуждение исходный текст |
Ответ на | Re: Changing the state of data checksums in a running cluster (Daniel Gustafsson <daniel@yesql.se>) |
Список | pgsql-hackers |
On Sat, Aug 16, 2025 at 09:34:03PM +0200, Daniel Gustafsson wrote: > Attached is a rebase on top of the func.sgml changes which caused this to no > longer apply. > > This version is also substantially updated with a new injection point based > test suite, fixed a few bugs (found by said test suite), added checkpoint to > disabling checksums, code cleanup, more granular wait events, comment rewrites > and additions and more smaller cleanups. I am very glad you went simple and didn't attempt restarting this process from the place it stopped: If the cluster is stopped while in <literal>inprogress-on</literal> mode, for any reason, then this process must be restarted manually. To do this, re-execute the function <function>pg_enable_data_checksums()</function> once the cluster has been restarted. The process will start over, there is no support for resuming work from where it was interrupted. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.
В списке pgsql-hackers по дате отправления: