Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id C670764FE1D for ; Wed, 15 Oct 2008 04:02:27 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 44546-06 for ; Wed, 15 Oct 2008 04:02:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from www.postnewspapers.com.au (www.postnewspapers.com.au [202.61.230.242]) by postgresql.org (Postfix) with ESMTP id 8DD7764FD91 for ; Wed, 15 Oct 2008 04:02:24 -0300 (ADT) Received: from mail.postnewspapers.com.au (202-89-185-120.static.dsl.amnet.net.au [202.89.185.120]) by www.postnewspapers.com.au (Postfix) with ESMTP id 6BA805C09E; Wed, 15 Oct 2008 15:02:18 +0800 (WST) Received: from [10.0.0.53] (wallace.localnet [10.0.0.53]) by mail.postnewspapers.com.au (Postfix) with ESMTP id 52CF81E0434; Wed, 15 Oct 2008 15:02:18 +0800 (WST) Message-ID: <48F5953C.2010108@postnewspapers.com.au> Date: Wed, 15 Oct 2008 15:01:16 +0800 From: Craig Ringer User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: Steve Crawford Cc: Rainer Mager , pgsql-performance@postgresql.org Subject: Re: speeding up table creation References: <000001c92e51$c42afcb0$4c80f610$@com> <48F531B9.9010302@pinpointresearch.com> In-Reply-To: <48F531B9.9010302@pinpointresearch.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200810/77 X-Sequence-Number: 31658 Steve Crawford wrote: > You cannot keep the data in memory (that is, you can't disable writing > to the disk). But since you don't care about data loss, you could turn > off fsync in postgresql.conf. From a test perspective you should be fine > - it will only be an issue in the event of a crash and then you can just > restart with a fresh load. Remember, however, that any performance > benchmarks won't translate to production use (of course they don't > translate if you are using ramdisk anyway). Another thing that may really help, if you're not already doing it, is to do all your schema creation inside a single transaction - at least assuming you can't use the template database approach. -- Craig Ringer