On Wed, 16 Jul 2003 03:54 pm, Bernie, CTA wrote: > Hi Peter, > > We use a modified (well hacked) version of PostgreSQL Replicator > and have experienced no significant problem. > > These were our primary DBMS replication requirements: > > 1. We needed a solution to operate securely within our > distributed data environment > 100 physical locations, and > 10,000 virtual datamarts. > > 2. We needed a replication topology that was scalable and > reliable with no single-point-of-failure, as present in most > DBMS Replication topologies. (Another reason why MySQL was not > attractive, as at the time only master-slave replication was > supported) > > 3. We required the ability to do asynchronous queries. > > 4. We required the metadata catalog and file replica catalog to > be distributed yet appear virtually centralized. > > 5. Since we were creating a virtual metadata catalog and a > unique autonomous security monitoring and incident handling > system, access to all of the source code was required. > > After looking at a few others� DBBALANCER > http://dbbalancer.sourceforge.net/ we picked PostgreSQL > Replicator http://pgreplicator.sourceforge.net/ and made a few > customized changes to the source to accommodate our unique > security monitoring and incident handling system. > > I am now in the early stages of planning a complete design of > our own PostgreSQL BDMS replicating technology featuring our > autonomous security monitoring and incident handling method. I > am not sure if the project will be a public or private.
I for one would love it to be public :-) -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
