From 8b476f7ba2b452830e430eca607850e29f0b3f91 Mon Sep 17 00:00:00 2001
From: Ulises Fierro <ufierro@gitlab.com>
Date: Tue, 26 Mar 2024 19:22:30 +0000
Subject: [PATCH] Added note about pg_shadow_loookup
Clarify that the function needs to be created when moving
from non-pgbouncer instances
---
doc/administration/postgresql/moving.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/doc/administration/postgresql/moving.md b/doc/administration/postgresql/moving.md
index 21184480541f0..fb0be46024f5b 100644
--- a/doc/administration/postgresql/moving.md
+++ b/doc/administration/postgresql/moving.md
@@ -47,6 +47,7 @@ To move databases from one instance to another:
/opt/gitlab/embedded/bin/psql -h $DST_PGHOST -U $DST_PGUSER -f gitlabhq_production.sql postgres
```
+1. Optional. If you migrate from a database that doesn't use PgBouncer to a database that does, you must manually add a [`pg_shadow_lookup` function](../gitaly/praefect.md#manual-database-setup) to the application database (usually `gitlabhq_production`).
1. Configure the GitLab application servers with the appropriate connection details
for your destination PostgreSQL instance in your `/etc/gitlab/gitlab.rb` file:
--
GitLab