On Fri, Dec 11, 2009 at 4:39 PM, Nikolas Everett <nik9...@gmail.com> wrote:
> > > > Fair enough. I'm of the opinion that developers need to have their unit > tests run fast. If they aren't fast then your just not going to test as > much as you should. If your unit tests *have* to createdb then you have to > do whatever you have to do to get it fast. It'd probably be better if unit > tests don't create databases or alter tables at all though. > > Regardless of what is going on on your dev box you really should leave > fsync on on your continuous integration, integration test, and QA machines. > They're what your really modeling your production on anyway. > The other common issue is that developers running with something like 'fsync=off' means that they have completely unrealistic expectations of the performance surrounding something. If your developers see that when fsync is on, createdb takes x seconds vs. when it's off, then they'll know that basing their entire process on that probably isn't a good idea. When developers think something is lightning, they tend to base lots of stuff on it, whether it's production ready or not. --Scott
