pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Craig Ringer <craig@postnewspapers.com.au>
To: Steve Crawford <scrawford@pinpointresearch.com>
Cc: Rainer Mager <rainer@vanten.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: speeding up table creation
Date: Wed, 15 Oct 2008 15:01:16 +0800
Message-ID: <48F5953C.2010108@postnewspapers.com.au> (raw)
In-Reply-To: <48F531B9.9010302@pinpointresearch.com>
References: <000001c92e51$c42afcb0$4c80f610$@com>
	<48F531B9.9010302@pinpointresearch.com>

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



view thread (4+ messages)

Message-ID: <48F5953C.2010108@postnewspapers.com.au>
Permalink:  ../48F5953C.2010108@postnewspapers.com.au/
Also on:    postgresql.org/message-id/48F5953C.2010108@postnewspapers.com.au

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: craig@postnewspapers.com.au, scrawford@pinpointresearch.com, rainer@vanten.com
  Subject: Re: speeding up table creation
  In-Reply-To: <48F5953C.2010108@postnewspapers.com.au>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox