opendev/gerrit
Code Issues Proposed changes

Also mention that MySQL can support replication, not just Postgres

Browse Source 
While I'm here, be consistent on the capitalization of MySQL in
the design document

Change-Id: I11e880e67c2e16daa72333b41d70f4518aa4394c
This commit is contained in:
Chad Horohoe
2012-05-06 22:28:45 -04:00
parent f93b3eecec
commit e9855b8f68
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/dev-design.txt
View File

@@ -87,7 +87,7 @@ and Git's own data integrity checks.
Each Git commit created on the client desktop system is converted
into a unique change record which can be reviewed independently.
Change records are stored in a database: PostgreSQL, MySql, or the
Change records are stored in a database: PostgreSQL, MySQL, or the
built-in H2, where they can be queried to present customized user
dashboards, enumerating any pending changes.
@@ -669,11 +669,11 @@ lag largely allows for some downtime in a disaster scenario.
Backups
~~~~~~~
PostgreSQL can be configured to save its write-ahead-log (WAL)
and ship these logs to other systems, where they are applied to
a warm-standby backup in real time. Gerrit instances which care
about reduduncy will setup this feature of PostgreSQL to ensure
the warm-standby is reasonably current should the master go offline.
PostgreSQL and MySQL can be configured to replicate their data to
other systems, where they are applied to a warm-standby backup in
real time. Gerrit instances which care about reduduncy will setup
this feature of PostgreSQL or MySQL to ensure the warm-standby is
reasonably current should the master go offline.
Gerrit can be configured to replicate changes made to the local
Git repositories over any standard Git transports. This can be