Merge branch 'docs-database-tier-badge' into 'master'

Add tier badges to Database doc pages

See merge request gitlab-org/gitlab!72390

doc/administration/postgresql/external.md

@@ -4,7 +4,7 @@ group: Database
 info: 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
 ---
 
-# Configure GitLab using an external PostgreSQL service
+# Configure GitLab using an external PostgreSQL service **(FREE SELF)**
 
 If you're hosting GitLab on a cloud provider, you can optionally use a
 managed service for PostgreSQL. For example, AWS offers a managed Relational

doc/administration/postgresql/index.md

@@ -2,26 +2,15 @@
 stage: Enablement
 group: Database
 info: 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
-type: reference
 ---
 
-# Configuring PostgreSQL for scaling
+# Configuring PostgreSQL for scaling **(FREE SELF)**
 
 In this section, you'll be guided through configuring a PostgreSQL database to
 be used with GitLab in one of our [reference architectures](../reference_architectures/index.md).
 There are essentially three setups to choose from.
 
-## PostgreSQL replication and failover with Omnibus GitLab **(PREMIUM SELF)**
-
-This setup is for when you have installed GitLab using the
-[Omnibus GitLab **Enterprise Edition** (EE) package](https://about.gitlab.com/install/?version=ee).
-
-All the tools that are needed like PostgreSQL, PgBouncer, and Patroni 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](replication_and_failover.md)
-
-## Standalone PostgreSQL using Omnibus GitLab **(FREE SELF)**
+## Standalone PostgreSQL using Omnibus GitLab
 
 This setup is for when you have installed the
 [Omnibus GitLab packages](https://about.gitlab.com/install/) (CE or EE),
@@ -29,7 +18,7 @@ to use the bundled PostgreSQL having only its service enabled.
 
 [> Read how to set up a standalone PostgreSQL instance using Omnibus GitLab](standalone.md)
 
-## Provide your own PostgreSQL instance **(FREE SELF)**
+## Provide your own PostgreSQL instance
 
 This setup is for when you have installed GitLab using the
 [Omnibus GitLab packages](https://about.gitlab.com/install/) (CE or EE),
@@ -37,3 +26,13 @@ or installed it [from source](../../install/installation.md), but you want to us
 your own external PostgreSQL server.
 
 [> Read how to set up an external PostgreSQL instance](external.md)
+
+## PostgreSQL replication and failover with Omnibus GitLab **(PREMIUM SELF)**
+
+This setup is for when you have installed GitLab using the
+[Omnibus GitLab **Enterprise Edition** (EE) package](https://about.gitlab.com/install/?version=ee).
+
+All the tools that are needed like PostgreSQL, PgBouncer, and Patroni 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](replication_and_failover.md)

doc/administration/troubleshooting/postgresql.md

@@ -2,10 +2,9 @@
 stage: Enablement
 group: Database
 info: 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
-type: reference
 ---
 
-# PostgreSQL
+# PostgreSQL **(FREE SELF)**
 
 This page contains information about PostgreSQL the GitLab Support team uses
 when troubleshooting. GitLab makes this information public, so that anyone can