On 03/20/2015 10:45 AM, Tom Lane wrote:
"Joshua D. Drake" <j...@commandprompt.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.
Fair enough. I am not going to name names but over the years (and just
today) I ran into another user that corrupted their database by turning
off fsync.
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.
How so? alter system fsync on/off (meta)
restart
That seems easier than editing the file and restarting?
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"
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
