Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id CA5B59F9B88 for ; Sat, 8 Sep 2007 15:22:28 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 56046-01 for ; Sat, 8 Sep 2007 15:22:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from dd1514.kasserver.com (dd1514.kasserver.com [85.13.128.107]) by postgresql.org (Postfix) with ESMTP id A8B3B9F9B53 for ; Sat, 8 Sep 2007 15:22:24 -0300 (ADT) Received: from [192.168.0.5] (p5089C509.dip.t-dialin.net [80.137.197.9]) by dd1514.kasserver.com (Postfix) with ESMTP id AD179285DDB; Sat, 8 Sep 2007 20:22:22 +0200 (CEST) Date: Sat, 08 Sep 2007 20:22:24 +0200 From: Bernd Helmle To: Tom Lane , "Joshua D. Drake" cc: Gregory Stark , Simon Riggs , mfatticcioni@mbigroup.it, pgsql-performance@postgresql.org Subject: Re: DRBD and Postgres: how to improve the perfomance? Message-ID: <02B6620CD34BA4D0F4A62C45@imhotep.credativ.de> In-Reply-To: <24337.1189269577@sss.pgh.pa.us> References: <2C070D1C3970467FF64F6B6A@imhotep.credativ.de> <1189232904.4281.19.camel@ebony.site> <87k5r1zd52.fsf@oxford.xeocode.com> <46E2CAAF.50205@commandprompt.com> <24337.1189269577@sss.pgh.pa.us> X-Mailer: Mulberry/4.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/152 X-Sequence-Number: 26697 --On Samstag, September 08, 2007 12:39:37 -0400 Tom Lane wrote: > However, it seems like the point here is not so much "can you recover > your data" as what a commit means. Do you want a commit reported to the > client to mean the data is safely down to disk in both places, or only > one? Yeah, that's what i meant to say. DRBD provides a handful other tweaks besides changing the sync protocol, i'd start with them first. You can get back experimenting with the sync protocol if there are still performance issues then. I don't hesitate changing to B as long as I'm aware that it changed semantics and I can deal with them. -- Thanks Bernd