Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 00FAD64FD6E for ; Tue, 14 Oct 2008 20:08:52 -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 59440-08 for ; Tue, 14 Oct 2008 20:08:46 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from ichigo.office.vanten.com (static-222-230-136-226.b-fam.svips.gol.ne.jp [222.230.136.226]) by postgresql.org (Postfix) with ESMTP id 7D6C964FDE5 for ; Tue, 14 Oct 2008 20:08:45 -0300 (ADT) Received: from rainerxp (rainer-xp.office.vanten.com [192.168.220.186]) by ichigo.office.vanten.com (Postfix) with ESMTP id 5CAA75081C for ; Wed, 15 Oct 2008 08:08:40 +0900 (JST) From: "Rainer Mager" To: Subject: speeding up table creation Date: Wed, 15 Oct 2008 08:08:27 +0900 Message-ID: <000001c92e51$c42afcb0$4c80f610$@com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C92E9D.3412A4B0" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AckuUcPcfyB1YoPnSyWe5bpQBFmYOQ== Content-Language: en-us X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200810/74 X-Sequence-Number: 31655 This is a multipart message in MIME format. ------=_NextPart_000_0001_01C92E9D.3412A4B0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I have an interesting performance improvement need. As part of the automatic test suite we run in our development environment, we re-initialize our test database a number of times in order to ensure it is clean before running a test. We currently do this by dropping the public schema and then recreating our tables (roughly 30 tables total). After that we do normal inserts, etc, but never with very much data. My question is, what settings can we tweak to improve performance is this scenario? Specifically, if there was a way to tell Postgres to keep all operations in memory, that would probably be ideal. We actually tried running Postgres off of a RAM disk and this did help a reasonable amount, but we're running under Windows and setting up the RAM disk is a hassle and all of our developers would need to do it. Any tips would be appreciated. --Rainer ------=_NextPart_000_0001_01C92E9D.3412A4B0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I have an interesting performance improvement need. = As part of the automatic test suite we run in our development environment, we re-initialize our test database a number of times in order to ensure it = is clean before running a test. We currently do this by dropping the public = schema and then recreating our tables (roughly 30 tables total). After that we = do normal inserts, etc, but never with very much data. My question is, what settings can we tweak to improve performance is this scenario? = Specifically, if there was a way to tell Postgres to keep all operations in memory, that = would probably be ideal.

 

We actually tried running Postgres off of a RAM = disk and this did help a reasonable amount, but we’re running under Windows = and setting up the RAM disk is a hassle and all of our developers would need = to do it.

 

 

Any tips would be appreciated.

 

 

--Rainer

------=_NextPart_000_0001_01C92E9D.3412A4B0--