DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=tfr0ICo1Fod0sJjCscPbQMN4fJwDSOuKb1sOCd8H9VGZ/pM6lkRMY3zUQNGv42UMH6DND9P586mAB54JxHGHsCSWREZQLXS2vZpV2a9i8wSkjKRDvTPYdGwqiFese1U81YrgWfwWAv+zf5CRK3AZwwPwIMSZN2meAP0TV7KHf3A=
Message-ID: <b42b73150709070556o22768ba5uc5ce260ebd2b10f2@mail.gmail.com>
Date: Fri, 7 Sep 2007 08:56:15 -0400
From: "Merlin Moncure" <mmoncure@gmail.com>
To: mfatticcioni@mbigroup.it
Subject: Re: DRBD and Postgres: how to improve the perfomance?
Cc: pgsql-performance@postgresql.org
In-Reply-To: <46E11BE4.6060500@mbigroup.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <46E11BE4.6060500@mbigroup.it>

On 9/7/07, Maila Fatticcioni <mfatticcioni@mbigroup.it> wrote:
> Obviously, working with the database in DRBD, we had two writes instead
> of only one but we are a bit disappointed about the low results. We
> would like to know if there is any way to improve the performance in
> order to have a 3/4 rate instead of the 1/2 one.

Have you considered warm standby PITR?   It achieves essentially the
same thing with very little overhead on the master.  The only downside
relative to DRDB is you have to think about the small gap between WAL
file rotations.  From what I understand, there is some new stuff
(check out skype skytools) that may help minimize this problem.

merlin