rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Minor wordsmithing in release notes' description of asynchronous commit.

This commit is contained in:
Tom Lane 2008-02-02 23:30:23 +00:00
parent 19c40492f0
commit 09bcb24806
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/src/sgml/release.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.577 2008/01/31 21:31:33 tgl Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.578 2008/02/02 23:30:23 tgl Exp $ -->
<!--
Typical markup:
@ -697,13 +697,14 @@ current_date &lt; 2017-11-17
<para>
This feature dramatically increases performance for short data-modifying
transactions. The disadvantage is that because disk writes are
delayed, if the operating system crashes before data is written to
the disk, committed data will be lost. This feature is useful for
transactions. The disadvantage is that because disk writes are delayed,
if the database or operating system crashes before data is written to
the disk, committed data will be lost. This feature is useful for
applications that can accept some data loss. Unlike turning off
<varname>fsync</varname>, asynchronous commit does not put database
consistency at risk; the worst case is that after a database or system
crash the last few reportedly-committed transactions might be missing.
<varname>fsync</varname>, using asynchronous commit does not put
database consistency at risk; the worst case is that after a crash the
last few reportedly-committed transactions might not be committed after
all.
This feature is enabled by turning off <varname>synchronous_commit</>
(which can be done per-session or per-transaction, if some transactions
are critical and others are not).