Commit 85f345be authored by Tom Lane's avatar Tom Lane

Improve grammar and spelling in durability discussion.

parent b34ee301
...@@ -1118,9 +1118,10 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse; ...@@ -1118,9 +1118,10 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse;
so if your site does not require such a guarantee, so if your site does not require such a guarantee,
<productname>PostgreSQL</productname> can be configured to run <productname>PostgreSQL</productname> can be configured to run
much faster. The following are configuration changes you can make much faster. The following are configuration changes you can make
to improve performance in such cases; they do not invalidate to improve performance in such cases. Except as noted below, durability
commit guarantees related to database crashes, only abrupt operating is still guaranteed in case of a crash of the database software;
system stoppage, except as mentioned below: only abrupt operating system stoppage creates a risk of data loss
or corruption when these settings are used.
<itemizedlist> <itemizedlist>
<listitem> <listitem>
...@@ -1159,8 +1160,8 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse; ...@@ -1159,8 +1160,8 @@ SELECT * FROM x, y, a, b, c WHERE something AND somethingelse;
<para> <para>
Turn off <xref linkend="guc-synchronous-commit">; there might be no Turn off <xref linkend="guc-synchronous-commit">; there might be no
need to write the <acronym>WAL</acronym> to disk on every need to write the <acronym>WAL</acronym> to disk on every
commit. This does enable possible tranaction loss in case of commit. This setting does risk transaction loss (though not data
a <emphasis>database</> crash. corruption) in case of a crash of the <emphasis>database</> alone.
</para> </para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment