Skip site navigation (1) Skip section navigation (2)

ChronicDB v3.0 offers easy-to-use replication for PostgreSQL

Posted on Aug. 2, 2010

Chandler, AZ —August 3, 2010— ChronicDB, the only software vendor that offers live database schema evolution with zero downtime, announced today version 3.0 of its software product that delivers a simplified approach to database replication for PostgreSQL.

Database replication is important for implementing hot-standby failover and for offloading parts of an organization's workflow, such as Extract-Transfer-Load (ETL) reporting, into an offline read-only database copy. With ChronicDB a simplified, highly automated replication system can be deployed without requiring a database administrator to read a 50+ page manual. Replication follows an asynchronous master/slave model, which is the most frequently requested model by organizations running mission-critical databases.

This technology is available for the first time for PostgreSQL. It is offered on Linux with plans to support other database and operating systems. ChronicDB is one of the easiest to administer replication systems ever offered for PostgreSQL with a FREE version available from chronicdb.com.

Complementing replication is the unique ability of ChronicDB to evolve a database schema or relocate a database while the database is actively used, without downtime, which has never been offered before by any software vendor. Live database relocation and live schema evolution are accomplished through sophisticated query rewritting and live connection migration.

With these capabilities ChronicDB allows multiple versions of database applications to execute concurrently and indefinitely against the same copy of the database. An end goal of ChronicDB is to offer semantically consistent version control for live databases, such as applying forward schema changes and efficiently reversing the changes if a defect is discovered in the application.

This post has been migrated from a previous version of the PostgreSQL website. We apologise for any formatting issues caused by the migration.


Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group