X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6894753500; Wed, 6 Apr 2005 09:16:23 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 65395-01; Wed, 6 Apr 2005 08:16:18 +0000 (GMT) Received: from cmailg3.svr.pol.co.uk (cmailg3.svr.pol.co.uk [195.92.195.173]) by svr1.postgresql.org (Postfix) with ESMTP id AD58453A09; Wed, 6 Apr 2005 09:16:17 +0100 (BST) Received: from modem-3774.leopard.dialup.pol.co.uk ([217.135.158.190] helo=192.168.0.102) by cmailg3.svr.pol.co.uk with esmtp (Exim 4.41) id 1DJ5hv-0007OF-B2; Wed, 06 Apr 2005 09:16:15 +0100 Subject: Re: Sustained inserts per sec ... ? From: Simon Riggs To: Christopher Petrilli Cc: Tom Lane , jd@commandprompt.com, "Marc G. Fournier" , pgsql-performance@postgresql.org In-Reply-To: <59d991c405040513055be3a9b2@mail.gmail.com> References: <20050401140421.P18194@ganymede.hub.org> <1112388818.3487.34.camel@jd2.commandprompt.com> <59d991c4050401125956d6069d@mail.gmail.com> <59d991c40504040648457808e9@mail.gmail.com> <26454.1112629979@sss.pgh.pa.us> <59d991c405040409094e7bbd17@mail.gmail.com> <26669.1112631807@sss.pgh.pa.us> <59d991c40504041846bc39a6@mail.gmail.com> <5217.1112668589@sss.pgh.pa.us> <1112730509.16721.918.camel@localhost.localdomain> <59d991c405040513055be3a9b2@mail.gmail.com> Content-Type: text/plain Organization: 2nd Quadrant Date: Wed, 06 Apr 2005 09:14:19 +0100 Message-Id: <1112775259.16721.1005.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.048 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200504/93 X-Sequence-Number: 11490 On Tue, 2005-04-05 at 16:05 -0400, Christopher Petrilli wrote: > On Apr 5, 2005 3:48 PM, Simon Riggs wrote: > > > The indicated fix of course is to increase shared_buffers. > > > > Splitting your tables at 4M, not 10M would work even better. > > Unfortunately, given we are talking about billions of rows > potentially, I'm concerned about that many tables when it comes to > query time. I assume this will kick in the genetic optimizer? No, it won't start using the genetic optimizer. You could just buy more RAM and keep table size the same. Best Regards, Simon Riggs