From: Tom Lane Date: Sat, 2 Feb 2008 23:30:23 +0000 (+0000) Subject: Minor wordsmithing in release notes' description of asynchronous commit. X-Git-Url: http://waps.l3s.uni-hannover.de/gitweb/?a=commitdiff_plain;h=c116de8ae1776fff3393f8c7ddc0416dd6563563;p=users%2Fbernd%2Fpostgres.git Minor wordsmithing in release notes' description of asynchronous commit. --- diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 25ffdf7eb7..0c34128c96 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -697,13 +697,14 @@ current_date < 2017-11-17 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 - fsync, 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. + fsync, 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 synchronous_commit (which can be done per-session or per-transaction, if some transactions are critical and others are not).