| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| 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-20 23:11:53 |
| Message-ID: | 550CA939.1090705@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/20/15 2:49 PM, Stephen Frost wrote:
> How about a big warning around fsync and make it more indepenent from
> the options around it?
+1, and the same for full_page_writes and wal_sync_method. I think
that's the best we can do at this point.
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.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-03-20 23:18:07 | Re: Remove fsync ON/OFF as a visible option? |
| Previous Message | David E. Wheeler | 2015-03-20 23:11:14 | Re: Patch: Add launchd Support |