| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| 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:45:25 |
| Message-ID: | 14322.1426873525@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> There are just as many people that are running with scissors that are
> now running (or attempting to run) our elephant in production.
Evidence please.
> Does it
> make sense to remove fsync (and possibly full_page_writes) from such a
> visible place as postgresql.conf?
> I don't think we should remove the features themselves but perhaps only
> have them settable via the new alter system command?
I would object to that, because it would make it vastly more difficult
to use fsync=off easily for development.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-03-20 17:47:41 | Re: Remove fsync ON/OFF as a visible option? |
| Previous Message | Pavel Stehule | 2015-03-20 17:43:59 | Re: proposal: searching in array function - array_position |