firebird/firebird-mirror
firebird/firebird-mirror
8
0
Fork 1
mirror of https://github.com/FirebirdSQL/firebird.git synced 2025-01-22 20:03:02 +01:00
Code Issues

Fixed mistake in the docs

Browse Source
This commit is contained in:
Dmitry Yemanov 2019-02-03 12:06:30 +03:00
parent 2f877baa9f
commit 8984d39125
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/README.replication.md
View File

@ -100,8 +100,8 @@ In the Beta 1 release, any physical copying method can be used:
Then the replica mode must be activated for the database copy. Two options are possible:
* gfix -replica read <database> -- set up database as read-only replica
* gfix -replica write <database> -- set up database as read-write replica
* gfix -replica read\_only <database> -- set up database as read-only replica
* gfix -replica read\_write <database> -- set up database as read-write replica
Read-only replica means that only the replicator connection can modify the database. This is mostly indended for high availability solutions as the replica database is guaranteed to match the master one and can be used for fast recovery. Regular user connections may perform any operations allowed for read-only transactions: select from tables, execute read-only procedures, write into global temporary tables, etc. Database maintenance such as sweeping, shutdown, monitoring is also allowed. This can be used for moving read-only load \(analytics, etc\) to the replica database. However, read-only connections may potentially conflict with the replication if some DDL statements \(those requiring an exclusing metadata lock\) are performed on the master database.