Re: Synchronous Log Shipping Replication - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Synchronous Log Shipping Replication
Date
Msg-id 1221231143.3913.1067.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Synchronous Log Shipping Replication  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Synchronous Log Shipping Replication  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Re: Synchronous Log Shipping Replication  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
On Fri, 2008-09-12 at 17:08 +0300, Heikki Linnakangas wrote:
> Simon Riggs wrote:

> I think we'll need an option to specify a maximum for the number of WAL 
> files to keep around. The DBA should set that to the size of the WAL 
> drive, minus some safety factor.
> 
> > It should be clear that to make this work you must run with a base
> > backup that was derived correctly on the current master. You can do that
> > by re-copying everything, or you can do that by just shipping changed
> > blocks (rsync etc). So I don't see a problem in the first place.
> 
> Hmm, built-in rsync capability would be cool. Probably not in the first 
> phase, though..

Built-in? Why? I mean make base backup using rsync. That way only
changed data blocks need be migrated, so much faster.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Transaction Snapshots and Hot Standby
Next
From: Csaba Nagy
Date:
Subject: Re: Synchronous Log Shipping Replication