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
edeb9463
Commit
edeb9463
authored
Apr 16, 2020
by
Anton Smith
Committed by
Achilleas Pipinellis
Apr 16, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Docs - Update pg_hba example for tracking Geo database
parent
dcd30541
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
13 additions
and
0 deletions
+13
-0
doc/administration/geo/replication/external_database.md
doc/administration/geo/replication/external_database.md
+13
-0
No files found.
doc/administration/geo/replication/external_database.md
View file @
edeb9463
...
@@ -145,6 +145,19 @@ outbound rules do not apply to RDS PostgreSQL databases. Therefore, you need to
...
@@ -145,6 +145,19 @@ outbound rules do not apply to RDS PostgreSQL databases. Therefore, you need to
rule to the read-replica's security group allowing any TCP traffic from
rule to the read-replica's security group allowing any TCP traffic from
the tracking database on port 5432.
the tracking database on port 5432.
1.
Ensure that your secondary node can communicate with your tracking database by
manually changing the
`pg_hba.conf`
that is associated with your tracking database.
Remember to restart PostgreSQL afterwards for the changes to take effect:
```plaintext
##
## Geo Tracking Database Role
## - pg_hba.conf
##
host all all <trusted tracking IP>/32 md5
host all all <trusted secondary IP>/32 md5
```
1.
SSH into a GitLab
**secondary**
server and login as root:
1.
SSH into a GitLab
**secondary**
server and login as root:
```
shell
```
shell
...
...
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