Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id DB1F11336DB6 for ; Sat, 9 Oct 2010 18:35:10 -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 74596-09 for ; Sat, 9 Oct 2010 21:35:04 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.123]) by mail.postgresql.org (Postfix) with ESMTP id 83626133655C for ; Sat, 9 Oct 2010 18:35:03 -0300 (ADT) X-Authority-Analysis: v=1.1 cv=iGF3DqghDyT/uy4mV2LvOKNXCATMSjL+tOl9cucoGVk= c=1 sm=0 a=uLnYnW5vPakA:10 a=JRZeEW2aRuwA:10 a=8nJEP1OIZ-IA:10 a=RAii6je2cdnAH6ATCOpc6g==:17 a=vnREMb7VAAAA:8 a=_Ixf_7qHAAAA:8 a=zzQQf5PzKVhq1zjPA1sA:9 a=u0CGbEP3wJv-AyqNds8A:7 a=xmSszqstEQ0vq9Ou0TgrTwa_xBMA:4 a=wPNLvfGTeEIA:10 a=ryAo9hy1-OkA:10 a=6vsjEBoLwlAA:10 a=0tfO7MgyNwYA:10 a=RAii6je2cdnAH6ATCOpc6g==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.73.87.196 Received: from [74.73.87.196] ([74.73.87.196:23628] helo=[192.168.1.100]) by hrndva-oedge03.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id 41/09-27923-600E0BC4; Sat, 09 Oct 2010 21:35:03 +0000 Message-ID: <4CB0E006.8010905@vmsinfo.com> Date: Sat, 09 Oct 2010 17:35:02 -0400 From: Mladen Gogala Reply-To: mladen.gogala@vmsinfo.com Organization: VMS User-Agent: Thunderbird 2.0.0.24 (X11/20100912) MIME-Version: 1.0 To: Florian Weimer CC: Greg Smith , Aaron Turner , pgsql-performance Subject: Re: large dataset with write vs read clients References: <4CAE3FDB.1040909@2ndquadrant.com> <87ocb3yu10.fsf@mid.deneb.enyo.de> In-Reply-To: <87ocb3yu10.fsf@mid.deneb.enyo.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201010/76 X-Sequence-Number: 40495 I have a logical problem with asynchronous commit. The "commit" command should instruct the database to make the outcome of the transaction permanent. The application should wait to see whether the commit was successful or not. Asynchronous behavior in the commit statement breaks the ACID rules and should not be used in a RDBMS system. If you don't need ACID, you may not need RDBMS at all. You may try with MongoDB. MongoDB is web scale: http://www.youtube.com/watch?v=b2F-DItXtZs Florian Weimer wrote: > * Greg Smith: > > >> Given the size of your database, I'd advise you consider a migration >> to a new version ASAP. 8.4 is a nice stable release at this point, >> that's the one to consider moving to. >> > > It also offers asynchronous commits, which might be a good tradeoff > here (especially if the data gathered is not used for billing purposes > 8-). > > -- Mladen Gogala Sr. Oracle DBA 1500 Broadway New York, NY 10036 (212) 329-5251 www.vmsinfo.com