From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 9.6 and fsync=off |
Date: | 2016-04-28 19:32:37 |
Message-ID: | CANP8+jLAph=Gk1hQy_+o8CvgxuHahZpgh7kqSy2LMq1+OsJS1A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 27 April 2016 at 17:04, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> On 27 April 2016 at 21:44, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Petr Jelinek <petr(at)2ndquadrant(dot)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.
>
If fsync=off and you turn it on, does it fsync anything at that point?
Or does it mean only that future fsyncs will occur?
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2016-04-28 19:36:56 | Re: [BUGS] Breakage with VACUUM ANALYSE + partitions |
Previous Message | Greg Stark | 2016-04-28 18:53:50 | Re: 9.6 and fsync=off |