On Jul 16, 2015, at 1:16 AM, Federico Capoano <federico.capo...@gmail.com> wrote:
> I also don't like the idea of believing django users are too stupid to > understand that this advice si valid for development only. Generally > python and django users are intelligent enough to properly read the > docs and understand what's written on it. It's not a matter of being "intelligent" or not. Developers are busy and can simply google things, see a particular line, and drop it in without fully understanding exactly what is going on. (Simply read this group for a while if you don't believe this to be the case!) People already turn off fsync, in production, after having read the PostgreSQL documentation, without actually realizing that they've put their database in danger. Among other things, developers often have local data in their PostgreSQL instance that is valuable, and advising them to do a setting that runs the risk of them losing that data seems like a bad idea. The Django documentation is not the place to go into the ramifications of fsync (or even synchronous_commit, although that's significantly less risky). -- -- Christophe Pettus x...@thebuild.com -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/44C44B64-1FD1-48A3-8DC8-ADD5BCCCA27C%40thebuild.com. For more options, visit https://groups.google.com/d/optout.
