Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
a93bada0
Commit
a93bada0
authored
Nov 14, 2016
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add prerequisites section to Geo docs
parent
a5bcbd78
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
13 additions
and
10 deletions
+13
-10
doc/gitlab-geo/database.md
doc/gitlab-geo/database.md
+13
-10
No files found.
doc/gitlab-geo/database.md
View file @
a93bada0
...
...
@@ -4,28 +4,31 @@ This document describes the minimal steps you have to take in order to
replicate your GitLab database into another server. You may have to change
some values according to your database setup, how big it is, etc.
The GitLab primary node where the write operations happen will connect to
`primary`
database server, and the secondary ones which are read-only will
connect to
`secondary`
database servers (which are read-only too).
>**Note:**
In many databases documentation you will see
`primary`
being references as
`master`
and
`secondary`
as either
`slave`
or
`standby`
server (read-only).
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
**Table of Contents**
-
[
PostgreSQL replication
](
#postgresql-replication
)
-
[
Prerequisites
](
#prerequisites
)
-
[
Step 1. Configure the primary server
](
#step-1-configure-the-primary-server
)
-
[
Step 2
- Configure the secondary server
](
#step-2--
-configure-the-secondary-server
)
-
[
Step 3
- Initiate the replication process
](
#step-3--
-initiate-the-replication-process
)
-
[
Step 2
. Configure the secondary server
](
#step-2
-configure-the-secondary-server
)
-
[
Step 3
. Initiate the replication process
](
#step-3
-initiate-the-replication-process
)
-
[
MySQL replication
](
#mysql-replication
)
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
## PostgreSQL replication
The GitLab primary node where the write operations happen will connect to
`primary`
database server, and the secondary ones which are read-only will
connect to
`secondary`
database servers (which are read-only too).
>**Note:**
In many databases documentation you will see
`primary`
being references as
`master`
and
`secondary`
as either
`slave`
or
`standby`
server (read-only).
### Prerequisites
The following guide assumes that:
-
You are using PostgreSQL 9.1 or later which includes the
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment