From: Craig Ringer <craig@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Petr Jelinek <petr@2ndquadrant.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Abhijit Menon-Sen <ams@2ndquadrant.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: 9.6 and fsync=off
Date: Wed, 27 Apr 2016 23:04:37 +0800
Message-ID: <CAMsr+YEy9zj2Nb_n8OFMAf2HpX-RVpb12sWYD2uakPy0Um9kag@mail.gmail.com> (raw)
In-Reply-To: <24748.1461764666@sss.pgh.pa.us>
References: <CAMsr+YGechDvrFj4xwoBWhJ7rW25Avqo+UqcyqbnS=LTFdGJ4g@mail.gmail.com>
<20160427104307.GA4861@toroid.org>
<CABUevExGL-FWNP0pyCH_9nY==i1ogP-v8XNXpQyDaEp7u4ypCA@mail.gmail.com>
<57209AE7.9020906@2ndquadrant.com>
<24748.1461764666@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 27 April 2016 at 21:44, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Petr Jelinek <petr@2ndquadrant.com> writes:
> > +1 (Abhijit's wording with data loss changed to data corruption)
>
> I'd suggest something like
>
> #fsync = on # flush data to disk for crash
> safety
> # (turning this off can cause
> # unrecoverable data corruption!)
>
>
Looks good.
The docs on fsync are already good, it's just a matter of making people
think twice and actually look at them.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: craig@2ndquadrant.com, tgl@sss.pgh.pa.us, petr@2ndquadrant.com, magnus@hagander.net, ams@2ndquadrant.com
Subject: Re: 9.6 and fsync=off
In-Reply-To: <CAMsr+YEy9zj2Nb_n8OFMAf2HpX-RVpb12sWYD2uakPy0Um9kag@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox