Received: from localhost.localdomain (postgresql.org [64.49.215.8])
	by localhost (Postfix) with ESMTP
	id EDD53476144; Wed,  8 May 2002 12:31:28 -0400 (EDT)
Received: from varsoon.wireboard.com (www.wireboard.com [216.151.155.101])
	by postgresql.org (Postfix) with ESMTP
	id 04D85476C46; Wed,  8 May 2002 11:03:05 -0400 (EDT)
Received: from doug by varsoon.wireboard.com with local (Exim 3.33 #1)
	id 175Sxg-0000Bs-00; Wed, 08 May 2002 11:02:36 -0400
To: holger@marzen.de
Cc: Martijn van Oosterhout <kleptog@svana.org>,
	"Samuel J. Sutjiono" <ssutjiono@wc-group.com>,
	<pgsql-general@postgresql.org>, <pgsql-sql@postgresql.org>
Subject: Re: Performance issues with compaq server
References: <Pine.LNX.4.44.0205080903080.11632-100000@bluebell.marzen.de>
From: Doug McNaught <doug@wireboard.com>
Date: 08 May 2002 11:02:35 -0400
In-Reply-To: Holger Marzen's message of "Wed,
 8 May 2002 09:05:50 +0200 (CEST)"
Message-ID: <m3offqk7hw.fsf@varsoon.wireboard.com>
Lines: 18
User-Agent: Gnus/5.0806 (Gnus v5.8.6) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Archive-Number: 200205/295
X-Sequence-Number: 24275

Holger Marzen <holger@marzen.de> writes:

> ACK. On a given hardware I get about 150 inserts per second. Using a
> begin/end transaction for a group of 100 inserts speeds it up to about
> 450 inserts per second.

COPY is even faster as there is less query parsing to be done, plus
you get a transaction per COPY statement even without BEGIN/END.

> But beware: if one insert fails (duplicate key, faulty data) then you
> have to re-insert the remaining rows as single transactions, else all
> rows of the previous transaction are discarded.

Hmm don't you have to ROLLBACK and redo the whole transaction without
the offending row(s), since you can't commit while in ABORT state?  Or
am I misunderstanding?

-Doug