Re: [GENERAL] Asychronous database replication

2005-09-18 Thread Scott Ribe
> But I find a surprisingly high fraction of applications are very amenable to > being handled as insert-only. A medical application strikes me as something > someone is all the more likely to be happy with an insert-only model. Yes, I work in the medical field, and use my own home-grown (predates

Re: [GENERAL] Asychronous database replication

2005-09-18 Thread Neil Dugan
On Friday 16 September 2005 07:28 am, John DeSoi wrote: > On Sep 15, 2005, at 9:54 PM, Greg Stark wrote: > > If you need data to propagate from the clients back to the server > > then things > > get more complicated. Even then you could side step a lot of > > headaches if you > > can structure the

Re: [GENERAL] Asychronous database replication

2005-09-16 Thread Greg Stark
John DeSoi <[EMAIL PROTECTED]> writes: > > If you need data to propagate from the clients back to the server then > > things > > get more complicated. Even then you could side step a lot of headaches if > > you > > can structure the application in specific ways, such as guaranteeing that > >

Re: [GENERAL] Asychronous database replication

2005-09-16 Thread Scott Ribe
> The requirements scream ASP model except that this system needs to be > functional for disaster management where it's likely there won't be any > communications. At least, that's the constraint I've been given. I'm not an expert on this, but just kicking around the idea, the approach I think I'

Re: [GENERAL] Asychronous database replication

2005-09-16 Thread Peter Fein
Steve Manes wrote: > Greg Stark wrote: > >> My first reaction to this description was to consider some sort of >> model where >> the master database publishes text dumps of the master database which are >> regularly downloaded and loaded on the slaves. The slaves treat those >> tables >> as purely

Re: [GENERAL] Asychronous database replication

2005-09-16 Thread Steve Manes
Greg Stark wrote: My first reaction to this description was to consider some sort of model where the master database publishes text dumps of the master database which are regularly downloaded and loaded on the slaves. The slaves treat those tables as purely read-only reference tables. If you n

Re: [GENERAL] Asychronous database replication

2005-09-16 Thread John DeSoi
On Sep 15, 2005, at 9:54 PM, Greg Stark wrote: If you need data to propagate from the clients back to the server then things get more complicated. Even then you could side step a lot of headaches if you can structure the application in specific ways, such as guaranteeing that the clients

Re: [GENERAL] Asychronous database replication

2005-09-15 Thread Greg Stark
Chris Browne <[EMAIL PROTECTED]> writes: > Well, what you clearly want/need is asynchronous multimaster... I didn't catch anything in his description that answered whether he needs multimaster or a simple single master with many slaves model would suffice. > I'm involved with Slony-I, which is

Re: [GENERAL] Asychronous database replication

2005-09-15 Thread Chris Browne
[EMAIL PROTECTED] (Steve Manes) writes: > I have a project on my plate which will involve potentially hundreds > of PG8 databases in the field which will need to synchronize data with > a central database. The company is a secular nonprofit which delivers > medical services to underprivileged kids

[GENERAL] Asychronous database replication

2005-09-15 Thread Steve Manes
I have a project on my plate which will involve potentially hundreds of PG8 databases in the field which will need to synchronize data with a central database. The company is a secular nonprofit which delivers medical services to underprivileged kids as well as to disaster victims like those h