Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 149721337B7D for ; Fri, 5 Nov 2010 08:27:51 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 73380-10 for ; Fri, 5 Nov 2010 11:27:44 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from www.postnewspapers.com.au (www.postnewspapers.com.au [173.230.139.50]) by mail.postgresql.org (Postfix) with ESMTP id 9C0D51335B36 for ; Fri, 5 Nov 2010 08:27:43 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by www.postnewspapers.com.au (Postfix) with ESMTP id 83A1914AA; Fri, 5 Nov 2010 07:27:43 -0400 (EDT) X-Virus-Scanned: amavisd-new at postnewspapers.com.au.com Received: from www.postnewspapers.com.au ([127.0.0.1]) by localhost (www.postnewspapers.com.au [127.0.0.1]) (amavisd-new, port 10024) with LMTP id WmEIJmtiEdYi; Fri, 5 Nov 2010 07:27:42 -0400 (EDT) Received: from mail.postnewspapers.com.au (ppp171-128.static.internode.on.net [150.101.171.128]) by www.postnewspapers.com.au (Postfix) with ESMTP id 77A352D; Fri, 5 Nov 2010 07:27:42 -0400 (EDT) Received: from [10.0.0.53] (wallace.localnet [10.0.0.53]) by mail.postnewspapers.com.au (Postfix) with ESMTP id 2DB08AEB45; Fri, 5 Nov 2010 19:27:41 +0800 (WST) Message-ID: <4CD3EA2D.3050403@postnewspapers.com.au> Date: Fri, 05 Nov 2010 19:27:41 +0800 From: Craig Ringer User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4 MIME-Version: 1.0 To: A B CC: pgsql-performance@postgresql.org Subject: Re: Running PostgreSQL as fast as possible no matter the consequences References: In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201011/49 X-Sequence-Number: 41073 On 05/11/10 18:59, A B wrote: > Hi there. > > If you just wanted PostgreSQL to go as fast as possible WITHOUT any > care for your data (you accept 100% dataloss and datacorruption if any > error should occur), what settings should you use then? Others have suggested appropriate parameters ("running with scissors"). I'd like to add something else to the discussion: have you looked at memcached yet? Or pgpool? If you haven't, start there. -- Craig Ringer Tech-related writing: http://soapyfrogs.blogspot.com/