database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-09-02 04:21:28 +03:00
Code Activity

Fix some typos, grammar and style in docs and comments

Browse Source 
The portions fixing the documentation are backpatched where needed.

Author: Justin Pryzby
Discussion: https://postgr.es/m/20210210235557.GQ20012@telsasoft.com
backpatch-through: 9.6
This commit is contained in:
Michael Paquier
2021-02-24 16:13:17 +09:00
parent 8ec8fe0f31
commit bcf2667bf6
30 changed files with 73 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
doc/src/sgml/wal.sgml
View File

@@ -237,19 +237,19 @@
</indexterm>
<para>
Data pages are not checksum protected by default, but this can optionally be
enabled for a cluster. When enabled, each data page will be assigned a
checksum that is updated when the page is written and verified every time
the page is read. Only data pages are protected by checksums, internal data
By default, data pages are not protected by checksums, but this can optionally be
enabled for a cluster. When enabled, each data page will be ASSIGNED a
checksum that is updated when the page is written and verified each time
the page is read. Only data pages are protected by checksums; internal data
structures and temporary files are not.
</para>
<para>
Checksums are normally enabled when the cluster is initialized using <link
Checksums verification is normally ENABLED when the cluster is initialized using <link
linkend="app-initdb-data-checksums"><application>initdb</application></link>.
They can also be enabled or disabled at a later time as an offline
operation. Data checksums are enabled or disabled at the full cluster
level, and cannot be specified individually for databases or tables.
level, and cannot be specified for individual databases or tables.
</para>
<para>
@@ -260,9 +260,9 @@
</para>
<para>
When attempting to recover from corrupt data it may be necessary to bypass
the checksum protection in order to recover data. To do this, temporarily
set the configuration parameter <xref linkend="guc-ignore-checksum-failure" />.
When attempting to recover from corrupt data, it may be necessary to bypass
the checksum protection. To do this, temporarily set the configuration
parameter <xref linkend="guc-ignore-checksum-failure" />.
</para>
<sect2 id="checksums-offline-enable-disable">