| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Houssais Hugues <Hugues(dot)Houssais(at)thomson(dot)net> |
| Cc: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Unify distant Postgres databases |
| Date: | 2006-05-15 21:38:54 |
| Message-ID: | 20060515213854.GQ26212@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, May 09, 2006 at 10:10:50AM +0200, Houssais Hugues wrote:
> Each distant database works on its own domain of data. Then no conflict should happen during updates.
> One thing I have not specified is that the distant databases don't handle global data but only data collected at the local level.
> Slony-1 seems not to provide replication from multi-partial databases to one global database. But maybe I'm wrong... Can you tell me more about this use of Slony?
Slony-I is in fact single-master. Slony-II will be multi-master, but
it's also vaporware right now.
What you can do is setup different tables for each set of local data and
replicate all of those back to a central location. That location can
then merge everything together and push it back out. You can also just
have each location be a master for it's local data and have all the
other locations subscribe to it.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-05-15 21:41:41 | Re: Exporting postgres query to CSV |
| Previous Message | Jim C. Nasby | 2006-05-15 21:21:45 | Re: What is your favorite front end for user interaction to postgresql databases? |