Re: [SQL] Replication - state of the art?

2006-03-01 Thread Andrew Sullivan
On Wed, Mar 01, 2006 at 04:15:18PM -0600, Jim C. Nasby wrote: > You could also use WAL shipping and some PITR trickery to keep a 'warm > standby' database up to date. How far behind it falls is up to you, > since you'll be periodically syncing the current WAL file to the backup > machine. Do the sy

Re: [SQL] Replication - state of the art?

2006-03-01 Thread Jim C. Nasby
You could also use WAL shipping and some PITR trickery to keep a 'warm standby' database up to date. How far behind it falls is up to you, since you'll be periodically syncing the current WAL file to the backup machine. Do the sync once a minute, and at most you lose 60 seconds of data. On Wed, Ma

Re: [SQL] Replication - state of the art?

2006-03-01 Thread Scott Marlowe
On Wed, 2006-03-01 at 11:51, Bryce Nesbitt wrote: > I'm interested in creating a mirror database, for use in case one our > primary machine goes down. Can people here help sort out which of the > several replication projects is most viable? > > As far as I can tell, the winner is slony1 at > http

Re: [SQL] Replication - state of the art?

2006-03-01 Thread Andrew Sullivan
On Wed, Mar 01, 2006 at 11:28:06AM -0800, Bryce Nesbitt wrote: > Actually let me loosen that a bit: we don't need two phase commit. We > can loose the most recent transaction, or even the last few seconds of > transactions. What we can't survive is -- on the day of the emergency > -- a long and

Re: [SQL] Replication - state of the art?

2006-03-01 Thread Bryce Nesbitt
Andrew Sullivan wrote: > On Wed, Mar 01, 2006 at 09:51:46AM -0800, Bryce Nesbitt wrote: > >> switch over and rebuild the DB. "No-lost transaction" is far more >> important than switch time. >> > > You can't guarantee that without two phase commit, no matter what you > do. Log shipping doe

Re: [SQL] Replication - state of the art?

2006-03-01 Thread Andrew Sullivan
On Wed, Mar 01, 2006 at 09:51:46AM -0800, Bryce Nesbitt wrote: > switch over and rebuild the DB. "No-lost transaction" is far more > important than switch time. You can't guarantee that without two phase commit, no matter what you do. Log shipping doesn't require you to have an active database r

[SQL] Replication - state of the art?

2006-03-01 Thread Bryce Nesbitt
I'm interested in creating a mirror database, for use in case one our primary machine goes down. Can people here help sort out which of the several replication projects is most viable? As far as I can tell, the winner is slony1 at http://gborg.postgresql.org/project/slony1/projdisplay.php , but t

Re: [SQL] Replication

2001-10-18 Thread Josh Berkus
Ray, > Does Postgres in anyway support replication? Will I be able to have > load-balancing between two postgres databases? Not at this time. GreatBridge was working on replication when they shut down. It's very likely that Red Hat will add replication once they get up to speed on Postgres, b

Re: [SQL] Replication

2001-10-18 Thread clayton cottingham
> "Hunter, Ray" wrote: > > Does Postgres in anyway support replication? Will I be able to have > load-balancing between two postgres databases? > > RAY HUNTER > Automated Test Group > Software Support Engineer > > ENTERASYS NETWORKS > > Internal: 53888 > Phone: 801 887-9888 > Fax:

[SQL] Replication

2001-10-18 Thread Hunter, Ray
Title: Replication Does Postgres in anyway support replication?  Will I be able to have load-balancing between two postgres databases? RAY HUNTER Automated Test Group Software Support Engineer   ENTERASYS NETWORKS   Internal: 53888 Phone:   801 887-9888 Fax:  801 972-5789 Cel