Subject: Re: Insert performance
From: Hannu Krosing <hannu@tm.ee>
To: shridhar_daithankar@persistent.co.in
Cc: pgsql-performance@postgresql.org
In-Reply-To: <3F40BDC4.1605.9407ADF@localhost>
References: <3F3E3B47.13828.333B51D9@localhost>
	<3F40BDC4.1605.9407ADF@localhost>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1061221963.2620.4.camel@fuji.krosing.net>
Mime-Version: 1.0
Date: Mon, 18 Aug 2003 18:52:43 +0300

Shridhar Daithankar kirjutas E, 18.08.2003 kell 09:21:
> On 16 Aug 2003 at 11:40, Josh Berkus wrote:
> 
> > Shridhar,
> > 
> > > Unfortunately he can not use copy due to some constraints. 
> > 
> > Why not use COPY to load the table, and then apply the constraints by query 
> > afterwords?  It might not be faster, but then again it might.
> 
> Lol.. The constraints I mentioned weren't database constraints.. 

Can't you still apply them later ;)

My own experimentation also got numbers in 9k/sec range (on a quad
1.3GHz Xeons, 2GM mem, 50MB/sec raid) when doing 10-20 parallel runs of
~1000 inserts/transaction.

Performance dropped to ~300/sec (at about 60M rows) when I added an
index (primary key) - as I did random inserts, the hit rates for index
pages were probably low.

--------------
Hannu