Skip site navigation (1) Skip section navigation (2)

Re: Getting even more insert performance (250m+rows/day)

From: "Daniel J(dot) Luke" <dluke(at)geeklair(dot)net>
To: "Dave Dutcher" <dave(at)tridecap(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Getting even more insert performance (250m+rows/day)
Date: 2006-05-24 20:08:06
Message-ID: DAFB8564-C235-4E36-A976-A01C9371E408@geeklair.net (view raw or flat)
Thread:
Lists: pgsql-performance
On May 24, 2006, at 4:02 PM, Dave Dutcher wrote:
> If you can live with possible database corruption, you could try  
> turning
> Fsync off.  For example if you could just reinsert the data on the off
> chance a hardware failure corrupts the database, you might get a  
> decent
> improvement.

I tried, but I didn't see much of an improvement (and it's not really  
acceptable for this application).

> Also have you tried creating the index after you have inserted all  
> your
> data?  (Or maybe copy already disables the indexes while inserting?)

The data gets inserted in batches every 5 minutes and I potentially  
have people querying it constantly, so I can't remove and re-create  
the index.

--
Daniel J. Luke
+========================================================+
| *---------------- dluke(at)geeklair(dot)net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+


In response to

Responses

pgsql-performance by date

Next:From: Daniel J. LukeDate: 2006-05-24 20:09:54
Subject: Re: Getting even more insert performance (250m+rows/day)
Previous:From: Steinar H. GundersonDate: 2006-05-24 20:03:49
Subject: Re: Getting even more insert performance (250m+rows/day)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group