DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=R39iFBbAbcMsRPhMiPddCQ+xRLAyEFVsAyY7GRB848Ts8br1u+gDKZRbSlO0nRNB+EEgBrhLssKQywpHHF8iWKZIOsjPjEDAcd5Q4b2vAHdHw//5+tcex6GYh2tY+duJnMyLMkt1jO50WNb661s6NN4ySm7CtaNApHGaKN5grcg=
Message-ID: <4326F406.7010402@gmail.com>
Date: Tue, 13 Sep 2005 08:45:10 -0700
From: Russ Brown <pickscrape@gmail.com>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050809)
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Re: Replication
References: <KGEFLMPJFBNNLNOOOPLGOEOGCIAA.simon@2ndquadrant.com>
In-Reply-To: <KGEFLMPJFBNNLNOOOPLGOEOGCIAA.simon@2ndquadrant.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Simon Riggs wrote:
> Barry,
> 
> You can use PITR to archive transaction logs to a second server that is
> kept in standby mode.
> 
> This will cope with any number of tables and cope with dynamic changes
> to tables.
> 
> This is fairly straightforward and very low overhead.
> Set archive_command to a program that transfers xlog files to second
> server.
> Then set restore_command on the second server to a program that loops
> until the next file is available.
> Switchover time is low.
> 

Apologies for going slighly off topic, but isn't this basically how 
MySQL does replication? I ask because one of the arguments against 
moving to PostgreSQL in my organisation is 'no replication out of the 
box'. But if the above is true it seems that all that is required are a 
couple of scripts to handle log transfer and you have a form of 
replication out of the box right there.

Or am I missing something?

-- 

Russ