On 03/20/2015 10:47 AM, Peter Geoghegan wrote:
>
> On Fri, Mar 20, 2015 at 9:52 AM, Joshua D. Drake <jd@commandprompt.com> wrote:
>> There are just as many people that are running with scissors that are now
>> running (or attempting to run) our elephant in production. Does it make
>> sense to remove fsync (and possibly full_page_writes) from such a visible
>> place as postgresql.conf?
>
> -1
>
> Anyone turning off fsync without even for a moment considering the
> consequences has only themselves to blame.
This is an extremely valid point. Shall we hand them a loaded gun with
the safety off too? We can't protect everyone but this is a rather
simple change that hurts nobody.
I am not going to raise a huge stink or anything but it seems rather simple.
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, @cmdpromptinc
Now I get it: your service is designed for a customer
base that grew up with Facebook, watches Japanese seizure
robot anime, and has the attention span of a gnat.
I'm not that user., "Tyler Riddle"
