Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 5FEE36329C6 for ; Tue, 10 Nov 2009 13:34:50 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 47131-04 for ; Tue, 10 Nov 2009 17:34:29 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by mail.postgresql.org (Postfix) with ESMTP id 4F93F6326D1 for ; Tue, 10 Nov 2009 13:34:39 -0400 (AST) Received: from [192.168.1.3] (pool-96-244-14-10.bltmmd.fios.verizon.net [96.244.14.10]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0MSHd5-1MfdRf1Ewl-00SwKw; Tue, 10 Nov 2009 18:34:37 +0100 Message-ID: <4AF9A425.9090102@2ndquadrant.com> Date: Tue, 10 Nov 2009 12:34:29 -0500 From: Greg Smith User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Laurent Laborde CC: Ivan Voras , pgsql-performance@postgresql.org Subject: Re: limiting performance impact of wal archiving. References: <8a1bfe660911100355l34a557ffj8244079c1fb689b5@mail.gmail.com> <8a1bfe660911100700l2a44f638m97ea6136b65deb21@mail.gmail.com> <8a1bfe660911100729q42ac732cga9bbadd52e2533dd@mail.gmail.com> <4AF99666.5090705@2ndquadrant.com> <8a1bfe660911100852l5573ab30ne91c6d8937dc836b@mail.gmail.com> In-Reply-To: <8a1bfe660911100852l5573ab30ne91c6d8937dc836b@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1/idrBd5Pe7N14sdbZ3BgJykhzeNo7lRHMbhor xezUGU45lqxXSdREv4r5rU8AcJJHEgbgvFvNnTs+DiaTYyuIia n0/uatShv/YG5h0UC6yVImIaqR8tbI/ X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.855 tagged_above=-10 required=5 tests=AWL=-0.745, BAYES_05=-1.11 X-Spam-Level: X-Archive-Number: 200911/112 X-Sequence-Number: 36280 Laurent Laborde wrote: > On Tue, Nov 10, 2009 at 5:35 PM, Greg Smith wrote: > > I have 1 spare dedicated to hot standby, doing nothing but waiting for > the master to fail. > + 2 spare candidate for cluster mastering. > > In theory, i could even disable fsync and all "safety" feature on the master. > There are two types of safety issues here: 1) Will the database be corrupted if there's a crash? This can happen if you turn off fsync, and you'll need to switch to a standby to easily get back up again 2) Will you lose transactions that have been reported as committed to a client if there's a crash? This you're exposed to if synchronous_commit is off, and whether you have a standby or not doesn't change that fact. > Everybody told me "nooo ! LVM is ok, no perceptible overhead, etc ...) > Are you 100% about LVM ? I'll happily trash it :) Believing what people told you is how you got into trouble in the first place. You shouldn't believe me either--benchmark yourself and then you'll know. As a rule, any time someone suggests there's a technological approach that makes it easier to manage disks, that approach will also slow performance. LVM vs. straight volumes, SAN vs. direct-attached storage, VM vs. real hardware, it's always the same story. -- Greg Smith greg@2ndQuadrant.com Baltimore, MD