Hi, While I'm not convinced this is the best solution, I have tested something similar, although it was never used in production (for other reasons).
As far as I know doing exactly what you describe is not possible, but what we did was have each DB replicate to a separate slave DB at the central site, then have triggers in place on those DBs that then copied rows as they were added into a consolidated database. Of course this doubles your storage requirements, which for us wasn't a problem as we needed the separate databases too. David. On Aug 14, 2007, at 4:13 PM, Benjamin Krajmalnik wrote: > I have a client who has 3 branches and a main office. > All activity is carried out at the branches, but the main office > needs read only access to a consolidated database. > Is it possible to set up the three branches as masters, pointing to > a single slave node (the main office)? > > _______________________________________________ > Slony1-general mailing list > [email protected] > http://gborg.postgresql.org/mailman/listinfo/slony1-general _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
