Re: Remove fsync ON/OFF as a visible option?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove fsync ON/OFF as a visible option?
Date: 2015-03-21 19:32:08
Message-ID: 550DC738.4020708@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 03/20/2015 04:11 PM, Jim Nasby wrote:

> As for why; Postgres already has a big reputation for being "hard to
> use" and "hard to setup". Leaving footguns laying around that could
> easily be warned about is part of the reason for that reputation.
> Reality is that there are a lot of people using Postgres that are
> nowhere close to being DBAs and making it easy for them to munch their
> data on accident doesn't help anyone.

Exactly.

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"

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Flower 2015-03-21 19:32:09 Re: Remove fsync ON/OFF as a visible option?
Previous Message Joshua D. Drake 2015-03-21 19:31:38 Re: Remove fsync ON/OFF as a visible option?