| From: | Alex Stapleton <alexs(at)advfn(dot)com> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Steve Bergman <steve(at)rueb(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Optimizing for writes. Data integrity not critical |
| Date: | 2005-05-21 15:16:30 |
| Message-ID: | 803159ED-9B03-43E0-ACE6-DC40E73D55C1@advfn.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)postgresql(dot)org
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Stapleton | 2005-05-21 17:27:18 | Re: Optimizing for writes. Data integrity not critical |
| Previous Message | Tomaz Borstnar | 2005-05-21 07:42:00 | Re: Error when try installing pgbench ? |