![]() We could not find any manuals for this topic, so hoped this article would be useful for professionals looking for such solution. ![]() Not so good news - if you are not running PostgreSQL on Debian/Ubuntu, you will have to build this utility from source. But what if your PostgreSQL version is prior to 11 or 12 and you need to check (enable/disable) checksums in the existed cluster? The good news - the utility is available in github and supports Postgres starting from 9.3. Since PostgreSQL 12, the utility was renamed to pg_checksums and now can enable, disable or check data checksums in a database cluster. In PostgreSQL 11, it became possible to check existed cluster using pg_verifiry_checksums utility. This can be done by specifying the "-data-checksums" option when initializing PostgreSQL cluster using initdb. So, PostgreSQL's developers strongly recommended to use this mechanism for production systems. The documentation says "Use checksums on data pages to help detect corruption by the I/O system that would otherwise be silent". Since version 9.3 PostgreSQL introduced the ability of checksums.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |