Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 59F44632CA0 for ; Fri, 11 Dec 2009 17:40:04 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 43620-10 for ; Fri, 11 Dec 2009 21:39:56 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f219.google.com (mail-ew0-f219.google.com [209.85.219.219]) by mail.postgresql.org (Postfix) with ESMTP id 35951632A1B for ; Fri, 11 Dec 2009 17:39:55 -0400 (AST) Received: by ewy19 with SMTP id 19so1507847ewy.21 for ; Fri, 11 Dec 2009 13:39:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=hciGYXXJLknH5woAd3c3Y7ts4TlSZRCHeXaaZngRkFE=; b=BxkSeo/nDOSv5zGAmuk4QGpWX+ladIBWhwC2gabjNdDkXWvRDQuihGOshJ8P6WEpVd KiC5bw8Rgd/GMJYhYMh3Dv8GbweJsXjlXtHIGPG4HqS0yqeEPi4iwFD4zLQ6ml1cwCo3 diM+CR/kwa9bIJCWINpQQNvb+MehTzfcb/69U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=hpaxc7XGkVJ/vVXOyxxN5fIJnECYVLjEFSoIdS6M91IgMYl75k61wyFQ/mC332uU4z rwTND+KTBKBPdECGjLvlGiJEo6+uN3tuxqb0hJ5NkLWM8p5OQgaXQEpQLgAsSShlmJ5N aXiqApzfnEWiJ3s9VxMwWDy4nsPqwzE+dWh2w= MIME-Version: 1.0 Received: by 10.216.91.20 with SMTP id g20mr743844wef.94.1260567594105; Fri, 11 Dec 2009 13:39:54 -0800 (PST) In-Reply-To: <1260564610.2611.41.camel@jd-desktop.unknown.charter.com> References: <4427a97a0912101235x3ade510blcc00d5ce9883c6b6@mail.gmail.com> <200912102256.59868.andres@anarazel.de> <4427a97a0912101401kb29e1a5ic5424d6d0b7efe62@mail.gmail.com> <200912102309.04057.andres@anarazel.de> <1260554319.2611.10.camel@jd-desktop.unknown.charter.com> <1260564610.2611.41.camel@jd-desktop.unknown.charter.com> From: Nikolas Everett Date: Fri, 11 Dec 2009 16:39:34 -0500 Message-ID: Subject: Re: 8.4.1 ubuntu karmic slow createdb To: jd@commandprompt.com Cc: Andres Freund , pgsql-performance@postgresql.org, Michael Clemmons Content-Type: multipart/alternative; boundary=0016e6d7eaeba97f6a047a7ac36f X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.598 tagged_above=-10 required=5 tests=BAYES_00=-2.599, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200912/154 X-Sequence-Number: 36768 --0016e6d7eaeba97f6a047a7ac36f Content-Type: text/plain; charset=ISO-8859-1 On Fri, Dec 11, 2009 at 3:50 PM, Joshua D. Drake wrote: > On Fri, 2009-12-11 at 15:43 -0500, Nikolas Everett wrote: > > Turning fsync off on a dev database is a bad idea? Sure you might > > kill it and have to start over, but thats kind of the point in a dev > > database. > > My experience is that bad dev practices turn into bad production > practices, whether intentionally or not. > 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. --0016e6d7eaeba97f6a047a7ac36f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Fri, Dec 11, 2009 at 3:50 PM, Joshua = D. Drake <jd@c= ommandprompt.com> wrote:
On Fri, 2009-12-11 at 15:43 -0500, Nikolas Everett wrote:=
> Turning fsync off on a dev database is a bad idea? =A0Sure you might > kill it and have to start over, but thats kind of the point in a dev > database.

My experience is that bad dev practices turn into bad production
practices, whether intentionally or not.

Fair enou= gh.=A0 I'm of the opinion that developers need to have their unit tests= run fast.=A0 If they aren't fast then your just not going to test as m= uch as you should.=A0 If your unit tests *have* to createdb then you have t= o do whatever you have to do to get it fast.=A0 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.= =A0 They're what your really modeling your production on anyway.
--0016e6d7eaeba97f6a047a7ac36f--