Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id ABB9E4764B5 for ; Wed, 8 May 2002 15:08:09 -0400 (EDT) Received: from blighty.com (m206-91.dsl.tsoft.com [198.144.206.91]) by postgresql.org (Postfix) with ESMTP id B74A247643C for ; Wed, 8 May 2002 13:43:34 -0400 (EDT) Received: by blighty.com (Postfix, from userid 1000) id 6C7BA683; Wed, 8 May 2002 10:53:08 -0700 (PDT) Date: Wed, 8 May 2002 10:53:08 -0700 From: Steve Atkins To: pgsql-general@postgresql.org Subject: Re: Performance issues with compaq server Message-ID: <20020508105308.A14127@blighty.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from doug@wireboard.com on Wed, May 08, 2002 at 11:02:35AM -0400 X-Archive-Number: 200205/303 X-Sequence-Number: 24283 On Wed, May 08, 2002 at 11:02:35AM -0400, Doug McNaught wrote: > Holger Marzen 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. Does anyone have any performance figures to hand on COPY vs BEGIN/INSERT/END, on indexed or unindexed tables? Cheers, Steve