From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
Cc: | Rainer Mager <rainer(at)vanten(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: speeding up table creation |
Date: | 2008-10-15 07:01:16 |
Message-ID: | 48F5953C.2010108@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Ivan Voras | 2008-10-15 09:30:40 | Re: Backup strategies |
Previous Message | Greg Smith | 2008-10-15 06:20:13 | Re: Drupal and PostgreSQL - performance issues? |