mirror of
https://github.com/postgres/postgres.git
synced 2026-10-23 13:29:09 +03:00
c05d5ce123
The feature to enable, or disable, data checksums in an online cluster saw a number of postcommit fixes during the beta period. Suspicions were raised about the risk of more issues surfacing after GA. To avoid shipping code which may have bugs, this reverts in full, or in part, the following commits:aaf8b9989f,cd857dec0e,5fee7cab1b,25b922ec58,8fb8ded889,b3a37ffbc5,abac86c7a2,3a18526e8d,01805b7d16,343d98c360,e469e4784e,8d22f52324,e5e1f6dc79,5ab239c9a9,0ca1b30105,9a39056c41,2018bd6167,1df361e3d8,bf25e5571b,381d19da15,b120358c61,07009121c2,d771b0a907,f19c0eccae,0907112d38,397f0fd06e,602f19c84c,e3a27cad46,4ae3e98c02,b364828f82A few bits remain as they have merit on their own: * The fix for offline checksums not preserving initial state in pg_control_init. The test case for this fix has been moved to src/bin/pg_checksums/t/002_actions.pl to survive the revert which removed the previous location. * When a page verification is logged, the additional note which informs if the buffer will be zeroed out was kept to aid any debugging around checksum failures. * The Data Checksum section in the docs was kept, but rewritten to reflect the current state. * The enum containing checksum states is kept and some hardcoded references to the off state (0) are replaced with the label PG_DATA_CHECKSUM_OFF instead. Discussion: https://postgr.es/m/E15AC050-C4B5-488D-BB2D-3C7AC9F89EA8@yesql.se Discussion: https://postgr.es/m/anwm6UPxoVS41QA2@bdtpg Discussion: https://postgr.es/m/CA+Tgmob9NY6m0YNFTQ4nFH2d0iC9SQRruDYxfndGKKzh8OC80w@mail.gmail.com Discussion: https://postgr.es/m/E07A611B-9CF3-4FDB-8CE8-A221E39040EC%40yesql.se