On 27/04/16 12:53, Magnus Hagander wrote:
On Wed, Apr 27, 2016 at 12:43 PM, Abhijit Menon-Sen <a...@2ndquadrant.com <mailto:a...@2ndquadrant.com>> wrote: At 2016-04-27 17:58:08 +0800, cr...@2ndquadrant.com <mailto:cr...@2ndquadrant.com> wrote: > > #fsync = on # turns forced synchronization on or off I suggest: # provide crash safety by flushing disk writes # (Disabling this can lead to unrecoverable data # loss if the system crashes.) +1 for the change. I suggest shortening it to just "disabling this can lead to unrecoverable data corruption" (I think corruption is better than loss, mainly because too many people equate loss with "i may loose my last 10 updates, and I'm fine with that).
+1 (Abhijit's wording with data loss changed to data corruption) -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
