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
3376af6b
Commit
3376af6b
authored
Jun 06, 2019
by
Marcel Amirault
Committed by
Evan Read
Jun 06, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Docs: Update anchor to more recent section in geo db doc
parent
ab095dea
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
2 deletions
+1
-2
doc/administration/geo/replication/database.md
doc/administration/geo/replication/database.md
+1
-2
No files found.
doc/administration/geo/replication/database.md
View file @
3376af6b
...
@@ -445,8 +445,7 @@ The replication process is now complete.
...
@@ -445,8 +445,7 @@ The replication process is now complete.
PostgreSQL connections. We recommend using PGBouncer if you use GitLab in a
PostgreSQL connections. We recommend using PGBouncer if you use GitLab in a
high-availability configuration with a cluster of nodes supporting a Geo
high-availability configuration with a cluster of nodes supporting a Geo
**primary**
node and another cluster of nodes supporting a Geo
**secondary**
node. For more
**primary**
node and another cluster of nodes supporting a Geo
**secondary**
node. For more
information, see the
[
Omnibus HA
](
../../high_availability/database.md#configure-using-omnibus
)
information, see
[
High Availability with GitLab Omnibus
](
../../high_availability/database.md#high-availability-with-gitlab-omnibus-premium-only
)
.
documentation.
For a Geo
**secondary**
node to work properly with PGBouncer in front of the database,
For a Geo
**secondary**
node to work properly with PGBouncer in front of the database,
it will need a separate read-only user to make
[
PostgreSQL FDW queries
][
FDW
]
it will need a separate read-only user to make
[
PostgreSQL FDW queries
][
FDW
]
...
...
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