Re: Optimizing for writes. Data integrity not critical - Mailing list pgsql-performance

From Alex Stapleton
Subject Re: Optimizing for writes. Data integrity not critical
Date
Msg-id 803159ED-9B03-43E0-ACE6-DC40E73D55C1@advfn.com
Whole thread Raw
In response to Re: Optimizing for writes. Data integrity not critical  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-performance
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
>
>


pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Tuning planner cost estimates
Next
From: Alex Stapleton
Date:
Subject: Re: Optimizing for writes. Data integrity not critical