| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 9.6 and fsync=off |
| Date: | 2016-04-27 10:53:04 |
| Message-ID: | CABUevExGL-FWNP0pyCH_9nY==i1ogP-v8XNXpQyDaEp7u4ypCA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 27, 2016 at 12:43 PM, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>
wrote:
> At 2016-04-27 17:58:08 +0800, craig(at)2ndquadrant(dot)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).
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2016-04-27 10:56:39 | Re: 9.6 and fsync=off |
| Previous Message | Abhijit Menon-Sen | 2016-04-27 10:43:07 | Re: 9.6 and fsync=off |