| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remove fsync ON/OFF as a visible option? |
| Date: | 2015-03-20 17:47:41 |
| Message-ID: | CAM3SWZR1HzGXgHHRBsRLhhXe0BcW5aAo2VhmzQjWoiOvRnv_rA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 20, 2015 at 9:52 AM, Joshua D. Drake <jd(at)commandprompt(dot)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. I can't imagine why you'd
want to remove full_page_writes or make it less visible either, since
in principle it ought to be perfectly fine to turn it off in
production once its verified as safe.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-03-20 18:07:55 | Re: assessing parallel-safety |
| Previous Message | Tom Lane | 2015-03-20 17:45:25 | Re: Remove fsync ON/OFF as a visible option? |