From: Alex Stapleton <alexs@advfn.com>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Steve Bergman <steve@rueb.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Optimizing for writes. Data integrity not critical
Date: Sat, 21 May 2005 16:16:30 +0100
Message-ID: <803159ED-9B03-43E0-ACE6-DC40E73D55C1@advfn.com> (raw)
In-Reply-To: <428D4146.6000203@familyhealth.com.au>
References: <428D1153.1020109@rueb.com>
<428D4146.6000203@familyhealth.com.au>
Is using a ramdisk in situations like this entirely ill-advised then?
When data integrity isn't a huge issue and you really need good write
performance it seems like it wouldn't hurt too much. Unless I am
missing something?
On 20 May 2005, at 02:45, Christopher Kings-Lynne wrote:
>> I'm doing the writes individually. Is there a better way?
>> Combining them all into a transaction or something?
>>
>
> Use COPY of course :)
>
> Or at worst bundle 1000 inserts at a time in a transation...
>
> And if you seriously do not care about your data at all, set fsync
> = off in you postgresql.conf for a mega speedup.
>
> Chris
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to
> majordomo@postgresql.org
>
>
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: alexs@advfn.com, chriskl@familyhealth.com.au, steve@rueb.com
Subject: Re: Optimizing for writes. Data integrity not critical
In-Reply-To: <803159ED-9B03-43E0-ACE6-DC40E73D55C1@advfn.com>
References: <428D1153.1020109@rueb.com> <428D4146.6000203@familyhealth.com.au> <803159ED-9B03-43E0-ACE6-DC40E73D55C1@advfn.com>
* 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