Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 9E19B2E3FFC for ; Tue, 5 Feb 2008 12:01:22 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 95810-02-8 for ; Tue, 5 Feb 2008 12:01:02 -0400 (AST) Received: from ptb-relay02.plus.net (ptb-relay02.plus.net [212.159.14.213]) by postgresql.org (Postfix) with ESMTP id 5BCC32E2E74 for ; Tue, 5 Feb 2008 11:59:30 -0400 (AST) Received: from [84.51.143.99] (helo=server3.office.archonet.com) by ptb-relay02.plus.net with esmtp (Exim) id 1JMQCi-0000S5-8p; Tue, 05 Feb 2008 15:59:24 +0000 Received: from [192.168.1.36] (dell36.office.archonet.com [192.168.1.36]) by server3.office.archonet.com (Postfix) with ESMTP id 0D9C827406F; Tue, 5 Feb 2008 15:59:23 +0000 (GMT) Message-ID: <47A887DB.3080002@archonet.com> Date: Tue, 05 Feb 2008 15:59:23 +0000 From: Richard Huxton User-Agent: Thunderbird 2.0.0.9 (X11/20071031) MIME-Version: 1.0 To: Simon Riggs CC: Dimitri Fontaine , pgsql-performance@postgresql.org, "Jignesh K. Shah" , Greg Smith Subject: Re: Benchmark Data requested References: <1202150236.4252.521.camel@ebony.site> <47A797E5.4000507@sun.com> <200802051506.51581.dfontaine@hi-media.com> <1202221496.4252.680.camel@ebony.site> <47A87618.1090203@archonet.com> <1202223268.4252.707.camel@ebony.site> <47A87B2E.7050205@archonet.com> <1202225207.4252.718.camel@ebony.site> In-Reply-To: <1202225207.4252.718.camel@ebony.site> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Plusnet-Relay: 1edb6627801a4f0a1b175e95536d4799 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/42 X-Sequence-Number: 28584 Simon Riggs wrote: > On Tue, 2008-02-05 at 15:05 +0000, Richard Huxton wrote: > >>> Only by locking the table, which serializes access, which then slows you >>> down or at least restricts other options. Plus if you use pg_loader then >>> you'll find only the first few rows optimized and all the rest not. >> Hmm - the table-locking requirement is true enough, but why would >> pg_loader cause problems after the first few rows? > > It runs a stream of COPY statements, so only first would be optimized > with the "empty table optimization". Ah, if you're allowing multiple commands during the process I can see how it could get fiddly. -- Richard Huxton Archonet Ltd