1.7 KiB
| stage | group | info | type |
|---|---|---|---|
| Enablement | Database | To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments | reference |
Configuring PostgreSQL for scaling
In this section, you'll be guided through configuring a PostgreSQL database to be used with GitLab in one of our reference architectures. There are essentially three setups to choose from.
PostgreSQL replication and failover with Omnibus GitLab (PREMIUM ONLY)
This setup is for when you have installed GitLab using the Omnibus GitLab Enterprise Edition (EE) package.
All the tools that are needed like PostgreSQL, PgBouncer, Patroni, and repmgr are bundled in the package, so you can it to set up the whole PostgreSQL infrastructure (primary, replica).
> Read how to set up PostgreSQL replication and failover using Omnibus GitLab
Standalone PostgreSQL using Omnibus GitLab (CORE ONLY)
This setup is for when you have installed the Omnibus GitLab packages (CE or EE), to use the bundled PostgreSQL having only its service enabled.
> Read how to set up a standalone PostgreSQL instance using Omnibus GitLab
Provide your own PostgreSQL instance (CORE ONLY)
This setup is for when you have installed GitLab using the Omnibus GitLab packages (CE or EE), or installed it from source, but you want to use your own external PostgreSQL server.