Message-ID: <4CB73736.3060308@iii.com>
Date: Thu, 14 Oct 2010 10:00:38 -0700
From: Dinesh Bhandary <dbhandary@iii.com>
Reply-To: dbhandary@iii.com
Organization: Innovative Interfaces
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: Re: replication solution
References: <4C73CD20.5040909@tech.sdb.it> <1287000387.1709.2649.camel@ebony>
In-Reply-To: <1287000387.1709.2649.camel@ebony>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

  I've heard that rubyrep (http://www.rubyrep.org) is a good tool for 
replication too. I think it has gained popularity because of its ease of 
use.
On a similar note I am eager to try postgreSQl 9.0 bulit in hot standby 
solution.I  can't really wait till Postgersql rolls out replicated 
solution which can also be used for a failover.


Dinesh

On 10/13/2010 1:06 PM, Simon Riggs wrote:
> On Tue, 2010-08-24 at 15:46 +0200, Silvio Brandani wrote:
>> Hi all,
>>
>> we are looking for a solution to create a replicated database to be used
>> as reporting database with same data of production ( we can accept a lag
>> of some minutes).
>>
>> we already have the Point In Time Recovery but we need a solution where
>> the standby is  always open in  readonly  , but the data is replicated
>> continuosly from primary.
>>
>> The Slony solution could be a possibility but the production database is
>> 80 Gb of data with  around 10000 transaction each hour.
>>
>> DO you have some suggestion for our implementaiont if exists??
> PostgreSQL 9.0 is production ready now and supports Hot Standby, which
> is exactly what you want.
>