* Joshua D. Drake (jd@commandprompt.com) wrote:
> On 03/20/2015 10:45 AM, Tom Lane wrote:
> >I would object to that, because it would make it vastly more difficult
> >to use fsync=off easily for development.
>
> How so? alter system fsync on/off (meta)
> restart
>
> That seems easier than editing the file and restarting?
If it's that easy then I'm not sure why you're thinking it'd stop users
from using it..
Now, if you wanted to remove it from the default/shipped
postgresql.conf (but do nothing else), then that might reduce the number
of people who change it without reading the docs, but we might actually
be better off by improving the docs in postgresql.conf to carry a clear
warning about the option.
At the moment, one could look at our default postgresql.conf and the
"turns forced synchronization on or off" and think it's something akin
or somehow related to synchronous_commit (which is completely different,
but the options are right next to each other..).
How about a big warning around fsync and make it more indepenent from
the options around it?
Thanks,
Stephen