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. On 14 Jul 2003 at 16:44, Peter Nixon wrote: > On Mon, 14 Jul 2003 04:24 pm, Bernie, CTA wrote: > > On 14 Jul 2003 at 10:30, Peter Nixon wrote: > > > Hi List > > > > > > I would like to take a quick straw poll. > > > > > > a) If you use a Database backend for FreeRadius which one do > > > you use? > > > > We are an BSDi / Open BSD environment>>> > > > > Accounting - Redundant Postgres DB > > == to other DBMS such as MySQL, Oracle its: > > 1. No license fee > > 2. Less Security Vulnerabilities > > 3. Easier to replacate > > 4. Lends to a Decentralized / Virtually Centralized DBMS > > topology, which is better for security applications > > 5. Better Transaction Processing Performance > > 6. Less overhead > > 7. Control of source > > 8. Scales well > > 9. Faster > > Yep. No arguements from me on these :-) For general purpose DB > work Postgres pretty much walks all over the competition when you > take all these factors into account. I can only imagine needing > to pay for a commercial DB if I was handling Terabytes of data. > (Postgres happily handles many gigabytes of data per table for me > currently) > > Do you mind telling me what replication system you use (Postgres > has several) and how you find it? Are there any gotchas/problems? > (I currently run my DBs standalone as I simply don't have the > reliability issues with postgres that used to force me to > replicate/cluster my MySQL boxes..) > > TIA > > -- > - - **************************************************** Bernie Chief Technology Architect Chief Security Officer [EMAIL PROTECTED] Euclidean Systems, Inc. ******************************************************* // "There is no expedient to which a man will not go // to avoid the pure labor of honest thinking." // Honest thought, the real business capital. // Observe> Think> Plan> Think> Do> Think> ******************************************************* - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
